Re: [OSM-talk] Why is JOSM upload so slow?
Hi, Martijn van Oosterhout wrote: > The 0.6 API wil have a bulk upload stream which can significantly > reduce the overhead. BTW, current JOSM versions already exclusively use bulk uploading for changes if the server speaks 0.6. There are a few conflict resolution/ error detection issues but I'm sure they'll be ironed out when 0.6 goes live. Bye Frederik -- Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09" E008°23'33" ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Why is JOSM upload so slow?
On Sat, Nov 15, 2008 at 9:34 AM, Keith Ng <[EMAIL PROTECTED]> wrote: > I see. Thanks for the information. > > When will the 0.6 API be ready and in use then? we're aiming for christmas. if anyone wants to help out with the server or client code, see the (mostly up-to-date) list of things on the wiki page http://wiki.openstreetmap.org/wiki/OSM_Protocol_Version_0.6 cheers, matt ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Why is JOSM upload so slow?
On Samstag 15 November 2008, Martijn van Oosterhout wrote: > On Sat, Nov 15, 2008 at 9:49 AM, Keith Ng <[EMAIL PROTECTED]> wrote: > > I am currently uploading fixed coastline from JOSM and I notice that the > > upload is excruciatingly slow. The maximum speech achievable is around > > 1.5KB/s and the average speed is around 800 byles/s. > > > > I am uploading data from Melbourne, Australia. There's nothing wrong with > > my Internet. My maximum upload bandwidth is 256KB/s. Yet, JOSM notifies > > me that my current upload will take around 95 minutes. > > The problem is not speed, it's latency. I'm not sure what your ping > time is to the server (I'm guessing near 350ms), but remember that any > single update done by JOSM will take at least a whole HTTP request to > do which is at least 4*RTT so maybe 1.5 seconds. Multiply by number of > objects... > > The 0.6 API wil have a bulk upload stream which can significantly > reduce the overhead. Another possibility is do a Save in JOSM and you > bulk_upload from a machine closer to the server. Somtimes working over a local squid helps improving Speed. This way squid might use one http/1.1 request to tunnel all http/1.0 requests over one tcp connection. -- Jörg (Germany, Tettnang) http://www.ostertag.name/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Why is JOSM upload so slow?
I see. Thanks for the information. When will the 0.6 API be ready and in use then? Regards, Keith On Sat, Nov 15, 2008 at 8:31 PM, Martijn van Oosterhout <[EMAIL PROTECTED]>wrote: > On Sat, Nov 15, 2008 at 9:49 AM, Keith Ng <[EMAIL PROTECTED]> wrote: > > I am currently uploading fixed coastline from JOSM and I notice that the > > upload is excruciatingly slow. The maximum speech achievable is around > > 1.5KB/s and the average speed is around 800 byles/s. > > > > I am uploading data from Melbourne, Australia. There's nothing wrong with > my > > Internet. My maximum upload bandwidth is 256KB/s. Yet, JOSM notifies me > that > > my current upload will take around 95 minutes. > > The problem is not speed, it's latency. I'm not sure what your ping > time is to the server (I'm guessing near 350ms), but remember that any > single update done by JOSM will take at least a whole HTTP request to > do which is at least 4*RTT so maybe 1.5 seconds. Multiply by number of > objects... > > The 0.6 API wil have a bulk upload stream which can significantly > reduce the overhead. Another possibility is do a Save in JOSM and you > bulk_upload from a machine closer to the server. > > Have a nice day, > -- > Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ > ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Why is JOSM upload so slow?
On Sat, Nov 15, 2008 at 9:49 AM, Keith Ng <[EMAIL PROTECTED]> wrote: > I am currently uploading fixed coastline from JOSM and I notice that the > upload is excruciatingly slow. The maximum speech achievable is around > 1.5KB/s and the average speed is around 800 byles/s. > > I am uploading data from Melbourne, Australia. There's nothing wrong with my > Internet. My maximum upload bandwidth is 256KB/s. Yet, JOSM notifies me that > my current upload will take around 95 minutes. The problem is not speed, it's latency. I'm not sure what your ping time is to the server (I'm guessing near 350ms), but remember that any single update done by JOSM will take at least a whole HTTP request to do which is at least 4*RTT so maybe 1.5 seconds. Multiply by number of objects... The 0.6 API wil have a bulk upload stream which can significantly reduce the overhead. Another possibility is do a Save in JOSM and you bulk_upload from a machine closer to the server. Have a nice day, -- Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Why is JOSM upload so slow?
On Saturday 15 November 2008 02:19:12 pm Keith Ng wrote: > So, why is uploading so slow? probably too many people uploading - it is one single server afaik. Try uploading when it is 2 am in Germany ;-) -- regards Kenneth Gonsalves Associate NRC-FOSS http://nrcfosshelpline.in/web/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Why is JOSM upload so slow?
I am currently uploading fixed coastline from JOSM and I notice that the upload is excruciatingly slow. The maximum speech achievable is around 1.5KB/s and the average speed is around 800 byles/s. I am uploading data from Melbourne, Australia. There's nothing wrong with my Internet. My maximum upload bandwidth is 256KB/s. Yet, JOSM notifies me that my current upload will take around 95 minutes. So, why is uploading so slow? ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
