try to cache proxy

[forki]

for a couple of users it seems to be very very slow to calc the proxy. see https://gitter.im/fsprojects/Paket discussion with @alexeyzimarev

[forki]

//cc @vasily-kirichenko could you please take a look?

[vasily-kirichenko]

Looks like an ordinary thread safe memoization. Maybe it is worth to extract memoze into some core module.

[forki]

the question is more: do you think it's enough to cache proxy per HTTP host?

[vasily-kirichenko]

No idea.

[forki]

fair enough ;-)

[forki]

I released this as 2.16.0-alpha001.
ypu can get it with paket.bootstrapper.exe prerelease

@alexeyzimarev, @alistair please check if it improves things

@vasily-kirichenko could you please verify that we don't break you

thanks everbody.

[forki]

@dnauck you are also behind proxy, right?

[alexeyzimarev]

I am at home now and have no proxy. Will be able to check tomorrow if I would reach my machine at work, I will be at another office for three days.

[alistair]

So I have just updated to the latest, cleaned cache and packages directory and run the following

https://gist.github.com/alistair/65cba5d92556e6f0457c

Time taken has dropped from 7 minutes to 1.

[dnauck]

@forki no .. not with my dev machine, cannot test

Most commercial proxy solutions have virus checking, so the first download and unzip of nuget packages for virus check could take a long time. If the package is too large or contains to many files it could also fail.

[alexeyzimarev]

I tested with 2.16.0 and it works splendidly 👍 46 seconds instead of seven minutes.

[forki]

Awesome. Thanks for all the help here.

[vasily-kirichenko]

Tested paket outdated on 2.16.0. Works OK, but I'm not sure it's faster.

[forki]

It's only faster for a handful of people where the proxy detection was
super slow. Most people (like myself) will not have perf gains. But I was
worried that caching might break things.
On Oct 23, 2015 8:55 AM, "Vasily Kirichenko" [email protected]
wrote:

Tested paket outdated on 2.16.0. Works OK, but I'm not sure it's faster.

—
Reply to this email directly or view it on GitHub
#1153 (comment).