gtg-contributors team mailing list archive
-
gtg-contributors team
-
Mailing list archive
-
Message #00262
Another simple performance test
Hi again,
I've added a parameter to gtg_stress_test (which I ran across doing that
d-bus service rename), to add large amounts of text to a task.
So you can do something like:
0. rm -rf tmp/
1. scripts/debug.sh
2. scripts/gtg_stress_test 1 10000
which adds one task with 10,000 words. Now try resizing the task
browser. Slow!! Try opening the task editor on that task. Oomph!!
With gtg_stress_test 1 1000, the browser seems to work fine, but the
task editor has troubles. Doubleclick on the task and taskeditor takes
some seconds to come up. Now try deleting or changing some text...
Oomph!!
With gtg_stress_test 100 100, both the browser and taskeditor are a bit
sluggish but seem to work okay. This is probably a more reasonable
workload for gtg, and probably what you want to use for optimizations.
If you want to really thrash your system, try: gtg_stress_test 10 10000
Warning: be prepared to kill -9 gtg!
Bryce