I haven't had time to go through all the aspseek code and doing so is like going through a web of confusing calls (ie, call sub 1, sub 1 calls sub 2 then back to sub 1 and then sub 3 - it's CraZY). I'm thinking (don't know for sure) that searching puts everything into an array instead of just using pointers to the results. A test run of aspseek with 5 million records along side another full text search via mysql table with 50 million records shows aspseek will consume most all available memory, but doing the same search on the other table using standard msql calls will only eat a small chunk and will return 30 million more results! I've had similar problems with aspseek using all available memory.
I think the search dameon by default runs 10 threads so that would explain the number of processes you see.
Regards,
Karen
Hi all,
First of all, is it normal, that in memory there are 3, 5, 10 "searchd -D" proccesses?
Some time ago, something strange begins with computer, where aspseek search is runing. Sometimes system load grows to 150:( I don't change anythingh on it, so I can't understand whats happening. But once, when I was online and was browsing server with telnet, I notice that system load began grows, and I advance to run "ps -aux". There was 3 searchd processes in memory, and each use 67% of memory... So, I disable searchd for few days, and everything was ok. Then I upgrate aspseek from 1.2.7 to 1.2.10, enable searchd and in few hours situation repeated:(
Anybody have ieas, whats happening, and how I can fix it, or at least how to find, what calls error?
Regards,
Ivan
_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
