Forum .LRN Q&A: Re: Help Needed in Setting up .LRN to Scale

Posted by Janine Ohmer on
Where did the extra time go?  Good question!  I just ran the same login again, and this time it looks like this:

+57.1 ms: Applied transformation from /web/product/www / dotlrn/index -> ? - 7.7 ms
+71.2 ms: Served file /web/product/packages/dotlrn/www/index.adp with adp_parse_ad_conn_file - 2937.4 ms
+3010.5 ms: Applied GET filter: (for /dotlrn/index ds_trace_filter) - 10.5 ms
returned filter_ok

So it's even slower this time, but the time spent in the database is still only 651 ms, 53 ms *less* than last time even though the overall time is roughly 800 ms longer.

The difference is all in serving the file, but there's nothing here to tell us why or how it took so much longer.  I imagine that's where the difference is between our numbers and yours, too.

Hmm. Will have to think about this.  Of course, if my hypothesis is correct and the system is out of RAM, then *everything* will be running somewhat slowly, so it's still possible that this is the problem, that nsd is just puttering along.

As far as the connections go, ideally those numbers would be increased but I don't think this system can handle any more connections, so I think it best to leave that as-is until we figure out the problem.

i will get back to you on the other questions.