[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] publicdb.gnumed.de performance
From: |
Sebastian Hilbert |
Subject: |
Re: [Gnumed-devel] publicdb.gnumed.de performance |
Date: |
Tue, 3 May 2011 20:32:14 +0200 |
User-agent: |
KMail/1.13.6 (Linux/2.6.38.2-19-default; KDE/4.6.0; i686; ; ) |
Am Sonntag, 1. Mai 2011, 20:01:33 schrieb Jim Busser:
> -- Jim
>
> On 2011-04-29, at 1:22 AM, Sebastian Hilbert wrote:
> > Hi all,
> >
> > I am looking for some real world figures
>
> On a 4-year old MacBook (2 GHz Core 2 Duo), from Vancouver Canada
>
> I am on a 2.5 Mbps download / 0.5 Mbps upload connection
> RTT(Y) 74 ms, Max delay 245 ms, test type socket/socket
>
> - GNUmed login window (select publicdb) to database connect prompt:
>
> about 20 seconds
>
> - completion of GNUmed plugin loading (allowing for language setting
> option)
>
> about 20 seconds
>
> - input Kirk & press enter --> to loading of Kirk
>
> about 1:10 (70 seconds) for the stopwatch cursor to normalize
> about another 20 seconds for the screen to update with Kirk & Kirk's
> tags
> (note the publicdb does not appear to switch from the inbox plugin)
>
> traceroute to publicdb.gnumed.de (94.101.41.9), 64 hops max, 52 byte
> packets 1 * * *
> 2 rd2bb-ge0-0-0-1.vc.shawcable.net (64.59.159.242) 12.999 ms 12.285 ms
> 24.870 ms 3 rc2bb-tge0-12-1-0.vc.shawcable.net (66.163.69.218) 11.370 ms
> 16.757 ms 12.826 ms 4 rc2ar-pos10-0.ed.shawcable.net (66.163.76.162)
> 35.563 ms 28.268 ms 29.566 ms 5 rc1we-tge0-1-0-0.ed.shawcable.net
> (66.163.70.29) 28.219 ms 33.118 ms 38.015 ms 6 66.163.78.66
> (66.163.78.66) 56.851 ms 43.748 ms 43.724 ms
> 7 rc1sh-pos15-0.mt.shawcable.net (66.163.76.221) 67.164 ms 67.867 ms
> 86.989 ms 8 rc1hu-pos2-0-0.ny.shawcable.net (66.163.76.54) 84.961 ms
> 78.993 ms 78.025 ms 9 rd1ny-ge5-0-0.ny.shawcable.net (66.163.74.21)
> 82.314 ms 81.954 ms 82.258 ms 10 xe-0-3-0-204.nyc30.ip4.tinet.net
> (213.200.66.233) 99.091 ms 89.597 ms 89.546 ms 11
> xe-8-2-0.fra21.ip4.tinet.net (89.149.184.85) 176.180 ms
> xe-0-3-1.fra21.ip4.tinet.net (89.149.186.37) 173.040 ms
> xe-0-0-0.fra21.ip4.tinet.net (89.149.186.181) 182.697 ms
> 12 hl-komm-gw.ip4.tinet.net (77.67.65.114) 165.303 ms 165.328 ms
> 166.489 ms 13 lma2.hlkomm.net (85.232.2.157) 178.024 ms 196.206 ms
> 180.266 ms 14 lma2.hlkomm.net (85.232.2.157) 181.358 ms 197.519 ms
> 217.955 ms 15 mail.hilbros.de (94.101.41.9) 178.786 ms 231.020 ms
> 181.071 ms
>
In your case ping time is roughly three times of what I get. So each data
package sent takes three times as long. This actually seems to be consistent
with your findings on GNUmed responsivenesse.
It takes you roughly 3 times as long to get the data. Shoving the data into
GNUmed is not the main bottleneck here I guess.
Compared to a the internet lines we were on a few years back it is hard to
believe that modern applications are still so slow when accessing the
database.
I wonder what can be done about it or if there can be done anything about it.
Sebastian