Skip to content
This repository has been archived by the owner on Jul 13, 2021. It is now read-only.

Objects larger than available memory #19

Open
jech opened this issue May 13, 2014 · 3 comments
Open

Objects larger than available memory #19

jech opened this issue May 13, 2014 · 3 comments

Comments

@jech
Copy link
Owner

jech commented May 13, 2014

There have been some reports of Polipo failing to properly serve objects larger than available memory, even in the absence of revalidation failures. (There's probably not much that can be done with uncachable objects without some major surgery to Polipo.)

@kaspar030
Copy link

Any updates on this? I've been running in this a lot. I'm trying to use polipo to accelerate downloading of large file (e.g., game patch files) by multiple users, on a route with little RAM.

With 1M of chunk memory and a 100M test file, starting multiple (>5) simultaneous downloads of that file causes clients to stall forever, polipo dropping the server connection, ...

@jech
Copy link
Owner Author

jech commented Nov 12, 2014

As far as I know, there's nobody working on that — feel free to try your hand at it. (Such questions are probably better sent to the mailing list.)

@YSL21
Copy link

YSL21 commented Sep 20, 2017

I know this is an old post but im getting this error. Anyone know how this can be fixed?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants