It doesn't appear to me while running "top -i" on the server that it is being heavily taxed. My initial thought was there was something wrong with the router until I loaded the Apache's default page and it loaded almost instantaneously so that seems to tell me the bottleneck is specific with ledgersmb. It would also seem to be specific to connecting via a computer and not directly from the server. I have ran these test from several browsers on my laptop along with my iPad all with the same results. My suspicion is the bottleneck is due to apache waiting for postgresql to respond, but I don't really have anything to base that on other than watching (i.e. tail -f) the Apache logs when their appears to be a delay before Apache's response gets written to the log. That being said, I don't know if just loading the
setup.pl page actually requires a connection to the database server. Has anybody else experienced this issue or anyone have any suggestions how best to troubleshoot this?