[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Maposmatic-dev] Database update becoming critical

From: Maxime Petazzoni
Subject: Re: [Maposmatic-dev] Database update becoming critical
Date: Tue, 8 Jun 2010 10:11:25 +0200
User-agent: Mutt/1.5.20 (2009-06-14)

* David Decotigny <address@hidden> [2010-06-08 09:08:51]:

> It would be very interesting to have some benchmarks about this. At
> first I was dubitative about that claim, but on second thoughts, maybe
> it's right (startup overhead higher, but working sets smaller on the
> other hand => scan/search/sort overheads perhaps smaller). The only
> closely-related benchmark I'm aware of is
> (thanks, Thomas), do you know of any other tests with osmosis in the loop ?

So I guess the bottomline of all this is that switching to SSD storage
would solve the problem. Switching to minutely diffs would be a plus,
reducing the latency between new data being imported in OSM and this
data being available for render on MapOSMatic.

> To test this... Is there a "COW" feature for pgsql which would allow us
> to run a few tests with the prod DB, without altering the data delivered
> to ocitysmap ? If not, I'm afraid we'd have to test on another machine.

I'll try to import the planet database on my machine and test the
minutely diffs (quad core, 4gb ram, standard 7200rpm SATA drives).

- Maxime
Maxime Petazzoni <>
 ``One by one, the penguins took away my sanity.''
Linux kernel and software developer at MontaVista Software

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]