Quote:
|
Originally Posted by Gizzy
Ok, can you try the test I placed earlier:
change yout FTP proxy to:
lutn-cache-2.server.ntli.net
try to download this file:
ftp://ftp.lom3europe.com/mir_install.zip
what speeds do you get?
then change FTP proxy to:
lutn-cache-2.server.ntli.net
what speeds do you get? |
I just downloaded that file at 2mb/s no cache specified, and from lutn-cache-2 at the same speed.
But the test is flawed. Because as I've said there is no default cache and I use lutn caches whether I put them in firefox or not, and as I've said twice, I don't have a problem.
Hoping I'm a ****head won't change that. Besides, I didn't just say you were wrong, I gave evidence and a test you could have done yourself to check what I said about the caches was correct and applied to you. I then had to repeat the same points and post a link. Spelling and grammar are the least of your problems, you can write it in Klingon for me, it won't change what I'm going to say.
That said, if there is a problem with a particular cache in lutn - and from time to time there certainly can be - it'd be easily solved and you would have done it already and the sun would be shining, skies blue and you wouldn't be trying to cancel.
Simply put, no amount of testing that cache is going to fix the problems in Luton with gaming. Nor is it really going to help because asking who uses that cache is widening the number of people beyond those with the problem, not narrowing it down. That was the reason I posted - but if that info wasn't helpful so be it.
Logically, for those of us using lutn caches, either downloading that file would use lutn-cache-2 if we don't specify a cache - which you seemed to believe earlier happens to all our requests. In which case I'd be testing nothing when I specified it. Or it doesn't use lutn-cache-2, in which case that file wouldn't be a problem even if that specific cache did have problems for the requests that do use it.
I'll bow out now anyway - someone as intelligent as yourself should be able to figure out what info to get to narrow it down from those who share the problem - but to answer dxl's question the chances seem high that there's not a lot you can do even if you narrow it down, other than wait for the engineers to sort out the problem.
