From: Jon Burgess <jburgess777@googlemail.com>
To: Viji V Nair <viji@fedoraproject.org>
Cc: Matija Nalis <mnalis-ml@voyager.hr>,
linux-ext4@vger.kernel.org, ext3-users@redhat.com
Subject: Re: optimising filesystem for many small files
Date: Sun, 18 Oct 2009 18:15:05 +0100 [thread overview]
Message-ID: <1255886105.27380.158.camel@localhost.localdomain> (raw)
In-Reply-To: <84c89ac10910180929t2bebfd3eq26eb318475a24fd4@mail.gmail.com>
On Sun, 2009-10-18 at 21:59 +0530, Viji V Nair wrote:
> On Sun, Oct 18, 2009 at 8:37 PM, Jon Burgess <jburgess777@googlemail.com> wrote:
> > On Sun, 2009-10-18 at 18:44 +0530, Viji V Nair wrote:
> >> >
> >> >> can see lots of system resources are free, memory, processors etc
> >> >> (these are 4G, 2 x 5420 XEON)
> >
> > 4GB may be a little small. Have you checked whether the IO reading your
> > data sources is the bottleneck?
>
> I will be upgrading the RAM, but I didn't see any swap usage while
> running this applications...
> the data source is on a different machine, postgres+postgis. I have
> checked the IO, looks fine. It is a 50G DB running on 16GB dual xeon
> box
Going into swap is not the issue. If you have extra RAM available then
the OS will use this as a disk cache which means the DB will be able to
access indexes etc without needing to wait for the disk every time. 16GB
of RAM for a 50GB DB should be sufficient if the data is sensibly
indexed.
> I have to give a try on mod_tile. Do you have any suggestion on using
> nginx/varnish as a cahce layer?
There have been some tests using squid as a cache in front of mod_tile.
This worked reasonably well but did not give a big performance increase
because the server was already able to handle the load without an
additional cache. If you want to discuss this further then I'd suggest
continuing the conversation on the OSM or Mapnik lists.
Jon
next prev parent reply other threads:[~2009-10-18 17:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 6:52 optimising filesystem for many small files Viji V Nair
2009-10-17 14:32 ` Eric Sandeen
2009-10-17 17:56 ` Viji V Nair
2009-10-17 22:26 ` Theodore Tso
2009-10-18 9:31 ` Viji V Nair
2009-10-18 11:25 ` Jon Burgess
2009-10-18 12:51 ` Viji V Nair
2009-10-18 11:41 ` Matija Nalis
2009-10-18 13:08 ` Fwd: " Viji V Nair
2009-10-19 7:23 ` Stephen Samuel (gmail)
2009-10-18 13:14 ` Viji V Nair
2009-10-18 15:07 ` Jon Burgess
2009-10-18 16:29 ` Viji V Nair
2009-10-18 17:15 ` Jon Burgess [this message]
2009-10-18 14:15 ` Peter Grandi
2009-10-18 16:10 ` Viji V Nair
2009-10-18 15:34 ` Eric Sandeen
2009-10-18 16:33 ` Viji V Nair
-- strict thread matches above, loose matches on Subject: below --
2009-10-17 6:59 Viji V Nair
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1255886105.27380.158.camel@localhost.localdomain \
--to=jburgess777@googlemail.com \
--cc=ext3-users@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mnalis-ml@voyager.hr \
--cc=viji@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).