On 26 October 2011 19:36, Max Bolingbroke wrote:
> So this is almost pure speculation, but perhaps adding (BS.length
> pkgStr `seq`) just before the liftIO on Mirror.hs:122 would reduce the
> memory usage significantly. Worth a try?
I made the change but after syncing for while (I continued where
On 26 October 2011 13:46, Bas van Dijk wrote:
> According to the profile most space is used by ARR_WORDS (which is the
> internal name for a ByteArray# if I remember correctly).
Interesting. There are a lot of ByteStrings in use in the server, so
candidates for a leak might be:
1. The cached cab
On 26 October 2011 00:18, Bas van Dijk wrote:
> I could run a sync on my 4GB laptop in the background tomorrow and do
> a heap profile. I do expect to kill it half way since I also have to
> get other stuff done.
I did a quick heap profile using -hy:
http://code.haskell.org/~basvandijk/hackage-s
On 25 October 2011 23:18, Bas van Dijk wrote:
> What kind[1] of heap profile would be most useful. (In my experience
> -hy or -hd are the most informative).
Either of those sound reasonable.
>> I'd like to try do this out
>> myself, but I can't mirror Hackage without hitting the usage limits on
On 25 October 2011 22:53, Max Bolingbroke wrote:
> Do you still see 4GB usage if you restart the server?
No, after restarting it was less but, if I remember correctly, still
over 700MB.
> Another thing to do would be to heap profile the server.. it would be
> very interesting to know what is goi
On 25 October 2011 20:23, Bas van Dijk wrote:
> Does this sound like a memory leak or does hackage-server actually
> require more than 4GB memory?
Wow!
The SoC student reported memory usage of about ~700MB with a full
import from the Hackage of the time:
http://cogracenotes.wordpress.com/page/2/
Hello,
What are the typical memory requirements to run hackage-server (as a
mirror of the current hackage).
The reason I ask is that I tried mirroring hackage on my 4GB desktop
machine. I let it mirror overnight but when I came back in the morning
the machine was completely unresponsive. It turne
