[Tilesathome] Renderability

[Jochen Frieling]

Hi,

> > The funny thing is, all of the RAM (2GB) gets eaten up by inkscape,
> > but none of the the swap space is touched at all. Right at the moment
> > of using 2GB RAM, it crashed.
> > Shouldn't Linux memory management use swap space just like RAM?
> > Maybe this exposes a problem in inkscape, not being able to use swap
> > correctly, or the like.
> >   
> OK -- Berlin is working but Den Haag is ... too much and constantly
> swapping here. No chance :-(

Oops, sorry Den Haag, not Rotterdam. I got that mixed up with Deelkar's
"benchmark tile":
> the "Rotterdam Tile" at z12 (2098,1354)

But the error showing up is the same. And it's not only AND data, there is
at least one TIGER tile (Boston area) with this problem as well.

If anyone is interested, here's an excerpt of the memory usage during
a crashing inkscape run (and a few invocations before that). It was
generated by logging the last line of output of the memstat command every
second:

1193174424  817984k
1193174425  831424k
1193174426  853232k
1193174427  862976k
1193174428 1071068k
1193174429 1972720k
1193174430 2103032k
1193174431 2228568k
1193174432  235872k
1193174433  291716k
...
1193174475  834156k
1193174476  847120k
1193174478  863180k
1193174479 1071212k
1193174480 1934860k
1193174481 2065288k
1193174482  108228k
1193174483  267156k
...
1193174555  843192k
1193174556  851588k
1193174557  856784k
1193174558 1074712k
1193174559 2444336k
1193174560 2709968k
1193174561  108232k
1193174562  285292k
...
1193174634  853588k
1193174635  861840k
1193174636  870248k
1193174637  895016k
1193174638 2146764k
*crash*
1193174639  43316k
1193174640  43312k
1193174641  43316k
1193174642  43316k

Greetings,
Jochen


-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger