[Rabbit-proxy-users] Re: OutOfMemoryError

[Robert O. <ro...@kh...>]

Sam wrote:

> Right now at any given time the load is about 25 users tops.

Ok, thats not very many. Depending on how active they are of course.
if they are on 28/56 kb lines they can not be very active.

> I have the cache set to 30 gigs but I think it is at about 60 megs 
> when that happens.
> It is normally around 60 megs. The index does not seem to get very big 
> but I guess it would if I actually used 30 gigs for cache.

The index file is a gzipped object stream, you can get a copy and gunzip 
it to see how big it is in
memory, Actually not really, but a quite good indication, for real 
information use a
java profiler. Since I develop a java profiler I tend to test it on 
rabbit so I have quite a
good idea on how rabbit behaves.

> This seems to happen every 24 hours, seems like exactly 24 hours.

That is not very odd. If your testers are trying that time every day...

> I will need to redirect to a file to get the further information.

Will wait for it.

Some statistics from a running rabbit:
Requests: 321 (quite newly started)
Total pages served: 320
WebConnections created: 202
Socket accepts: 40

External connections: 0, 16 different sites

Cached files: 696 (cache from previous session included).
Cache size: 1 279 929

Used java heap: 2 038 072
current java heap: 4 050 944 (=> currently about 2 MB free).
Total objects in memory: 46 215.

The three biggest entries:
char[]: 9339 instances, 923 576 bytes
String: 9982 instances  (some strings share the char[]), 239568 bytes
Headers: 13865 (one header has a key and a value: "Accept" "text/html", 
share strings). 221 840 bytes.

cache.index 92 809 bytes
du -k on /tmp/rcache: 3532

So if we assume that rabbits heap will grow linearly with the cache size 
(I do not think that this
is the case, but lets assume that it does). Then you would need a heap 
size of ~100 MB (50*1.2 = 60)
So it may be that you need to give rabbit more memory.

/robo