One thing I should remember is that before I start measuring things likeiSCSI performance, I should check to make sure that I'm actually using agigabit Ethernet connection. Conversely, if I get unexpectedly terriblehigh-level performance, perhaps I should make a point of immediatelychecking the network speed. Especially if the terrible performance isaround 10 megabytes a second.

(This is especially embarrassing when I forget this for the second time.)

This can happen to us for a combination of two reasons; first,

One of the long-standing splits for dynamic websites is between dynamiccontent rendering and static content rendering (where you use trickslike 404 handlers to generate a page'scontent only once, write it to a static file, and then afterwards justserve the static file).

(This assumes that static rendering is viable; for heavilypersonalized sites it may be more trouble than it's worth,if you are already effectively never generating the samepage twice anyways.)

Fundamentally the choice is tradeoff of

I think I may have finally woken up to a (potential) cause for my random NumLock issues : the xine media player. Oneindicator, one that I really should have paid attention to earlier, isthat often starting xine will turn on NumLock (and sometimes turn itoff immediately afterwards). It is of course hard to be entirely suresince the problem is erratic, but I've been doing some testing sinceI noticed the correlation and I don't think I've ever had the problemwhen