Its an exciting day for me, because at long last NCT Search 3.0 is in a real serious QA mode. Right now, I'm hammering on it with 20 concurrant sessions, each posting search after search after search (10,000 times) without pause. What I'm looking for, is under those conditions do I loose memory, does the performance degrade to unusable levels, or does it just plain crash? So far, 30 minutes in, its looking rock solid. Memory usage is holding steady and average response time is hanging in around 45 seconds. Now, 45 seconds is a LONG time to wait for a search -- but if you understand concurrancy and do the math this test is roughly the equivilant of a server handling something close to 50,000 searches per day -- which is pretty big. This is a dual processer 700mhz machine (a speed daeman in its day) :-) --- but not something you'd host a site that big on. I'll be happy if it doesn't melt under that load. Regular use response times are ending up around 3 seconds which is very workable.
Wish me luck!
--AP
ohh....followup -- It looks like Tomcat is only using 1 of the two processors to do this. I can tell, W2K says that processor is just pegged at full for 'java.exe' lol. The other process is free for my Domino server. That bodes well for performance on faster machines. A single 700mhz machine doing this is COOL.
;-)
Comment Entry |
Please wait while your document is saved.