[Tilesathome] Long Request Take Time?

[Florian Lohoff]

On Wed, Sep 10, 2008 at 03:20:58PM -0500, Ian Dees wrote:
> 
> On Wed, Sep 10, 2008 at 3:16 PM, Ed Loach <ed at loach.me.uk> wrote:
> > I think this is an improvement; it means we seem to have clients
> > ready to start servicing the level 1 and 2 requests almost as soon
> > as they come in (when all is running smoothly that is), and the
> > level 4 requests are getting dealt with without the upload queue
> > filling and causing everything to choke up.
> >
> 
> But this means my CPUs are sitting idle with no work to do, and I'm paying
> for their power and heat to do nothing. I'd rather see them doing preemptive
> renders of highly-edited areas or rendering those prio4 requests than
> sitting idle.
> 
> How many requests per second is the TAH server able to handle? It doesn't
> seem like shuffling this sort of data around would be too much work, but I
> didn't pay attention to those huge discussions about tileset-per-file
> earlier. Did we cover this issue then?

Before the change your client was waiting on upload - now its waiting to
get a request - its not that much of a change. The advantage is that
high priority tiles which get rendered also immediatly get uploaded as
there always will be empty upload slots. So for prio1/2 we get the
latency down.

Yes - the goal should be that the bottleneck to always be the clients to
keep them busy all the time but this needs more work to be done and the
empty prio4 brought everything out of balance.

Flo
-- 
Florian Lohoff                  flo at rfc822.org             +49-171-2280134
	Those who would give up a little freedom to get a little 
          security shall soon have neither - Benjamin Franklin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.openstreetmap.org/pipermail/tilesathome/attachments/20080911/0c526b79/attachment.pgp>