Opened 9 years ago
Closed 8 years ago
#611 closed defect (fixed)
Session format: compare performance of msgpack vs. pickle
| Reported by: | Scooter Morris | Owned by: | Greg Couch |
|---|---|---|---|
| Priority: | critical | Milestone: | Alpha2 |
| Component: | Input/Output | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | 609, 609 | |
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
Once we have a msgpack session implementation, we need to compare the performance of it vs. our current approach.
Change History (5)
comment:1 by , 9 years ago
| Blocking: | 609 → 609, 609 |
|---|
comment:2 by , 9 years ago
| Component: | Unassigned → Input/Output |
|---|
comment:3 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:4 by , 8 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
For 4v8r, 85% of the restore time is in _RestoreManager.resolve_references(). Need equivalent of state.FinalizedState for restores.
comment:5 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
After putting FinalizedState object output, only 1.2% of time was spent in _RestoreManager.resolve_references(). In this case, there was a 6X speed up.
Note:
See TracTickets
for help on using tickets.
Here are some preliminary results using a session file that only has 4v8r in it (128780 atoms and 130160 bonds -- no ribbons):
v1 sessions use pickle, v2 session use msgpack
File size:
Speed: