Closed
Bug 776767
Opened 13 years ago
Closed 13 years ago
differences between funkload and grinder tests
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rfkelly, Unassigned)
References
Details
(Whiteboard: [qa+])
I have done a comparison of the funkload and grinder loadtest scripts, and there are some differences worth noting/thinking about:
1) grinder POSTs batches of 10 items; funkload POSTs batches of 100 items.
2) grinder doesn't hit the "tabs" collection; funkload does hit it.
3) grinder occasionally does a DELETE; funkload never does a DELETE.
4) grinder will sometimes POST an update to an existing record; funkload always creates new records.
5) grinder often requests /meta/global; funkload never will.
Item (1) is probably enough to explain the failing loadtests we have been seeing, as this produces a ~10 times increase in write operations in the database. Discussion suggests that 100 items per batch is closer to realistic behaviour, so I will file a separate bug to hash that out.
We should think about the other items and whether we need to port the grinder behaviour over to funkload. At least item (3) should definitely be ported over.
Updated•13 years ago
|
Whiteboard: [qa+]
| Reporter | ||
Comment 1•13 years ago
|
||
Most of these are included in the patch to Bug 782002
Depends on: 782002
| Reporter | ||
Comment 2•13 years ago
|
||
Closing this out, the majority of these were fixed by Bug 782002 and we have more specific bugs open for the remaining actions.
No longer depends on: 776777
Comment 3•13 years ago
|
||
:rfkelly can you mark this as Resolved/Fixed then?
| Reporter | ||
Comment 4•13 years ago
|
||
Whoops, must have added the comment but forgot to update the status
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 5•13 years ago
|
||
Thanks. Based on Comment 2, marking this as Verified.
Status: RESOLVED → VERIFIED
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•