Feature #2087
closed
lightweight filestore workload generator
Added by Sage Weil about 12 years ago.
Updated about 12 years ago.
Description
simple program that uses FileStore and generates something that looks vaguely like what an OSD does. e.g.,
- stream of transactions with something like
- small(or large) write to new object
- setxattr on that object
- append to per-collection log object
- set collection xattr
do that with say 50 parallel streams to different collections.
- Target version changed from v0.43 to v0.44
- Translation missing: en.field_position set to 1138
- Translation missing: en.field_story_points set to 5
- Translation missing: en.field_position deleted (
1138)
- Translation missing: en.field_position set to 1138
- Assignee set to Samuel Just
- Assignee changed from Samuel Just to Joao Eduardo Luis
Mark suggested that this would be a good talk for Joao.
- Status changed from New to In Progress
- Target version changed from v0.44 to v0.45
- Translation missing: en.field_position deleted (
1150)
- Translation missing: en.field_position set to 8
- Translation missing: en.field_position deleted (
13)
- Translation missing: en.field_position set to 12
- Translation missing: en.field_position deleted (
10)
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 1167
- Status changed from In Progress to 4
- Status changed from 4 to 7
- Status changed from 7 to In Progress
Looks like some memory should be leaking bad, such that valgrind hangs on exit.
19080
19080 HEAP SUMMARY:
19080 in use at exit: 9,454,160,343 bytes in 68,984 blocks
19080 total heap usage: 973,116 allocs, 904,132 frees, 19,001,241,545 bytes allocated
19080
^C^C^C^C^C^C
- Status changed from In Progress to 7
Memory leak fixed.
Apparently, the FileStore does not cleanup after transactions once they are applied, which may lead to huge memory leaks.
Now we simply 'delete m_tx' in the transaction's callback class.
Valgrind still reports memory leaks, but they seem to come from the FileStore class instead of being directly related with our WorkloadGenerator class.
- Status changed from 7 to Resolved
Also available in: Atom
PDF