G'day, all. I've found two small threads with a problem similar to mine in the archives [1,2], and in both of them Juliusz replied that this is a known bug where downloading stalls if an object is larger than available memory and there is no on-disk cache. But my download also stalls if I am using on-disk cache, the server supports caching, only the server is on a faster line than I am. Why can't polipo use its on-disk cache when it goes out of memory and complete the download? Am I missing something? I did this:
darcs get http://www.pps.jussieu.fr/~jch/software/repos/polipo mkdir /tmp/{www,cache} make LOCAL_ROOT=/tmp/www DISK_CACHE_ROOT=/tmp/cache ./polipo export http_proxy=localhost:8123 wget http://archlinux.puzzle.ch/iso/latest/archlinux-2008.06-core-i686.img Downloading stalled after chunkHighMark bytes, and polipo started complaining with: Short on chunk memory -- attempting to punch holes in the middle of objects. My download rate was ~150 KB/s. Btw., polipo managed fine after midnight, when my ISP stopped throttling and the download rate reached ~3 MB/s. But sometimes I could still reproduce the problem when downloading with wget --limit-rate=400K. When looking at the archives, it appeared that there are at least some people here using polipo in an environment with many users. Aren't you experiencing this problem? Or you're giving polipo lots of memory to work with? [1] http://article.gmane.org/gmane.comp.web.polipo.user/2249 [2] http://article.gmane.org/gmane.comp.web.polipo.user/1850 -- -- Rogutės Sparnuotos ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Polipo-users mailing list Polipo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/polipo-users
