> > I'm not an expert in debugging web applications. Here are my two cent:
> > We once had a problem when we hosted very large logbooks (several 10 thousands of entries) that the server would run
> > out of real memory and was slowed down by swapping. Therefore my first idea would be to monitor the server: Is
> > the CPU load peaking? What happens with the memory consumption? Any other suspicious process running on the server?
> > But it could be as well a network or browser problem. Did you try different browsers?
> > Did you check the elogd log file?
> 
> The logbook only has a few hundred entries, elogd is using only around 20-30 MB and there is enough free RAM. The load 
> average for the server is around 0.2, elogd only uses 5% CPU at most when it is accessed and the CPU is idle most of the 
> time. 
> 
> Strangely it happens mostly when using Chrome, and almost never with Firefox. I captured the network traffic, but I can't 
> see anything unusual. It just takes very long until the answer is returned by the elogd server.

My tuppance worth.  I have noticed (firefox) that some attachments take rather longer than might be expected to upload.  I
originally thought this was the ghostview program processing say a pdf to make pngs etc, but have more recently started to
question that assumption.  No solution or much clue, just another observation.