When logging out of your desktop session, you want all programs to shut down quickly. Strigi is one of the programs that can linger while it is analyzing a file. I’ve done some work to improve this latency and have measured the current latency after some improvements to analyzers that can potentially take long on some files.
Here is a graph with the analyzer latencies of my current version:
You can see that there is a 5% chance that stopping an analysis takes more than one second.
This graph is just an example. Regardless of statistics, it should
never take more than one second to shutdown an analysis. So I’m going to
try to eliminate all delays longer than one second. Detecting the delays
can be done with a simple
assert(timeSinceLastCheckpoint() < 1) in the checkpoint
function. Finding which analyzer should do more checkpointing might be a
bit harder.
Comments
assert
does this mean the program will just crash if not assert(timeSinceLastCheckpoint() < 1) ? That would make a bad user experience.
Thorsten
--
wait, wait. There is a new Mexico ?
By tstaerk at Thu, 02/07/2008 - 07:48
crash
Yes, the program latencytesteer will crash. This is a tool that will go in strigi/src/dummyindexer in your build directory.
Of course there is no assert in any code that gets installed and distributed.
By Jos van den Oever at Thu, 02/07/2008 - 08:12