Is anyone out there successfully using the redundant SplitFile insertion/ retrieval functionality in fproxy? I haven't gotten any complaints which isn't usually a good sign.
I am curious if people are seeing memory problems. The encoder and decoder plugins have to load the data that they operate on into memory. They may use up to 24M of RAM at the high water mark per encode or decode task. This memory is only used while the encoding / decoding is taking place. I expect it will be garbage collected relatively quickly after encoding/decoding finishes. I am not sure that JVM implementations are guaranteed to give the memory back to the OS in a timely manner. For what it's worth, performance seems entirely acceptable on both my test systems (P233 192M / P800 128M). I'm thinking of putting click through warning page for SplitFile downloads into fproxy, like the one for unknown mime types. That way an evil site author couldn't bog down your system by creating a page with links to a bunch of large redundant SplitFiles. --gj -- Freesites (0.3) freenet:MSK at SSK@enI8YFo3gj8UVh-Au0HpKMftf6QQAgE/homepage// (0.4) freenet:SSK at npfV5XQijFkF6sXZvuO0o~kG4wEPAgM/homepage// _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
