Desired characteristics of requests to "tabs" collection in sync loadtests?

NEW
Unassigned

Status

Cloud Services
Server: Sync
6 years ago
2 years ago

People

(Reporter: rfkelly, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Reporter)

Description

6 years ago
The sync loadtests do not currently make any requests to the "tabs" collection.

Since this collection is stored in couchbase rather than mysql, it has different performance characteristics.  Just naively adding it into the existing loadtest setup seems to saturate couchbase write load.

We should decide on some simulated characteristics for this collection, then add it into the test.  For example, desired item size dsitribution, frequency of reads/writes relative to other collections.

cc'ing client devs for additional perspective.
Whiteboard: [qa+]
Tabs will be uploaded on almost every sync, and thus also all records but our own will be fetched on every sync. Each client provides one record, so we can assume an average of 1 or 2 records per collection (with highs of, say, 10?).

Each record will be large:

{"clientName":"John's Firefox on PC3600",
 "tabs":[{"title":"Slashdot", "urlHistory":["http://slashdot.org"], "icon":"http://slashdot.org/favicon.ico"}, …]}

so 100+ chars per tab. Users have between 1 and maybe 500 tabs open, with the mean and median being around 5. Power users like me will be around 300.

Naturally, I'll hit the max size for a WBO (256K), because our tabs format sucks :)

HTH!
OS: Linux → All
Hardware: x86 → All
(Reporter)

Updated

5 years ago
Blocks: 875552
Anything we want for Sync 1.5?
Priority: -- → P3
Priority: P3 → --
You need to log in before you can comment on or make changes to this bug.