user@domain.invalid wrote:
> I found on the internet a pdf file helping to double the speed of firefox.
>
> Is this really possible, and if so than why isn't it implemented
> standard in Firefox?

Could you share this secret with all of us so we can enjoy the benefits
too? I'm using the FasterFox extension (http://fasterfox.mozdev.org/) and
it makes a noticeable difference.

Don Nickell schreef:
> user@domain.invalid wrote:
>> I found on the internet a pdf file helping to double the speed of
>> firefox.
>>
>> Is this really possible, and if so than why isn't it implemented
>> standard in Firefox?
>
> Could you share this secret with all of us so we can enjoy the benefits
> too? I'm using the FasterFox extension (http://fasterfox.mozdev.org/)
> and it makes a noticeable difference.


Ik copied the text from the PDF (which I downloaded from the newsgroup alt.binaries.e-book
(The PDF also contained pictures)

(Does anybody know if it works, and if so why isn't implemented standard in Firefox.)

See for the text below.


--------------------------------------

Now here are some Tips&Tricks that can help you double the speed of Firefox.

1. Type about:config in the address bar and then press Enter.

2. In the filter search bar type network.http.pipelining. Be sure the value field is set
true,if not double-click to set true.
HTTP is the application-layer protocol that most web pages are transferred with. In
HTTP 1.1, multiple requests can be sent before any responses are received. This is known
as pipelining. Pipelining reduces page loading times, but not all servers support it.

3. Go back to the filter search bar and type network.http.pipelining.maxrequests.
Double-click this option and set its value to 8.

4. In the filter search bar and type network.http.proxy.pipelining. Once opened doubleclick
on it and set it to true.

5. In IPv6-capable DNS servers, an IPv4 address may be returned when an IPv6 address
is requested. It is possible for Mozilla to recover from this misinformation, but a
significant delay is introduced.
Type network.dns.disableIPv6 in the filter search bar and set this option to true by
double clicking on it.

6. CONTENT INTERRUPT PARSING
This preference controls if the application will interrupt parsing a page to respond to UI
events. It does not exist by default.
Right-click (Apple users ctrl-click) anywhere in the about:config window, select New
and then Boolean from the pop-up menu. Then:
A. Enter content.interrupt.parsing in the New boolean value pop-up window and click
OK
B. When prompted to choose the value for the new boolean, select true and click OK.

7. Rather than wait until a page has completely downloaded to display it to the user,
Mozilla applications will regularly render what has been received to that point. This
option controls the maximum amount of time the application will be unresponsive while
rendering pages.
Right-click (Apple users ctrl-click) anywhere in the about:config window, select New
and then Integer from the pop-up menu.
A. Enter content.max.tokenizing.time in the New integer value pop-up window and
click OK
B. You will be prompted to enter a value. Enter 2250000 and click OK.

8. CONTENT NOTIFY INTERVAL
This option sets the minimum amount of time to wait between reflows. Right-click
(Apple users ctrl-click) anywhere in the about:config window, select New and then
Integer from the pop-up menu.
A. Type content.notify.interval in the New integer value pop-up window and click OK.
B. You will be prompted to enter a value. Enter 750000 and click OK.

9. CONTENT NOTIFY ONTIMER
A. This option sets if to reflow pages at an interval any higher than that specified by
content.notify.interval. Right-click (Apple users ctrl-click) anywhere in the
about:config window and select New and then Boolean from the pop-up menu.
B. Type content.notify.ontimer in the New boolean value pop-up window and click OK.
C. You will be prompted to choose the value for the new boolean. Select true and click
OK.

10. Notify Backoffcount
This option controls the maximum number of times the content will do timer-based
reflows. After this number has been reached, the page will only reflow once it is finished
downloading. Right-click (Apple users ctrl-click) anywhere in the about:config window
and select New and then Integer from the pop-up menu.
A. Enter content.notify.backoffcount in the New integer value pop-up window and click
OK.
B. You will be prompted to enter a value. Enter 5 and click OK.

11. CONTENT SWITCH THRESHOLD
You can interact with a loading page when content.interrupt.parsing is set to true.
When a page is loading, the application has two modes: a high frequency interrupt mode
and a low frequency interrupt mode. The first one interrupts the parser more frequently to
allow for greater UI responsiveness during page load.
The low frequency interrupt mode interrupts the parser less frequently to allow for
quicker page load. The application enters high frequency interrupt mode when you move
the mouse or type on the keyboard and switch back to low frequency mode when you had
no activity for a certain amount of time. This preference controls that amount of time.
Right-click (Apple users ctrl-click) anywhere in the about:config window and select
New and then Integer from the pop-up menu.
A. Enter content.switch.threshold in the New integer value pop-up window and click
OK.
B. You will be prompted to enter a value. Enter 750000 and click OK.

12. NGLAYOUT INITIALPAINT DELAY
Mozilla applications render web pages incrementally, they display what’s been received
of a page before the entire page has been downloaded. Since the start of a web page
normally doesn’t have much useful information to display, Mozilla applications will wait
a short interval before first rendering a page. This preference controls that interval. Rightclick
(Apple users ctrl-click) anywhere in the about:config window and select New and
then Integer from the pop-up menu.
A. Enter nglayout.initialpaint.delay in the New integer value pop-up window and click
OK.
B. You will be prompted to enter a value. Enter 0 and click OK.

user@domain.invalid wrote:
> Don Nickell schreef:
>> user@domain.invalid wrote:
>>> I found on the internet a pdf file helping to double the speed of
>>> firefox.
>>>
>>> Is this really possible, and if so than why isn't it implemented
>>> standard in Firefox?
>>
>> Could you share this secret with all of us so we can enjoy the
>> benefits too? I'm using the FasterFox extension
>> (http://fasterfox.mozdev.org/) and it makes a noticeable difference.
>
>
> Ik copied the text from the PDF (which I downloaded from the newsgroup
> alt.binaries.e-book
> (The PDF also contained pictures)
>
> (Does anybody know if it works, and if so why isn't implemented standard
> in Firefox.)
>
> See for the text below.
>
>
> --------------------------------------
>
> Now here are some Tips&Tricks that can help you double the speed of
> Firefox.
>
> 1. Type about:config in the address bar and then press Enter.
>
> 2. In the filter search bar type network.http.pipelining. Be sure the
> value field is set
> true,if not double-click to set true.
> HTTP is the application-layer protocol that most web pages are
> transferred with. In
> HTTP 1.1, multiple requests can be sent before any responses are
> received. This is known
> as pipelining. Pipelining reduces page loading times, but not all
> servers support it.
>
> 3. Go back to the filter search bar and type
> network.http.pipelining.maxrequests.
> Double-click this option and set its value to 8.
>
> 4. In the filter search bar and type network.http.proxy.pipelining. Once
> opened doubleclick
> on it and set it to true.
>
> 5. In IPv6-capable DNS servers, an IPv4 address may be returned when an
> IPv6 address
> is requested. It is possible for Mozilla to recover from this
> misinformation, but a
> significant delay is introduced.
> Type network.dns.disableIPv6 in the filter search bar and set this
> option to true by
> double clicking on it.
>
> 6. CONTENT INTERRUPT PARSING
> This preference controls if the application will interrupt parsing a
> page to respond to UI
> events. It does not exist by default.
> Right-click (Apple users ctrl-click) anywhere in the about:config
> window, select New
> and then Boolean from the pop-up menu. Then:
> A. Enter content.interrupt.parsing in the New boolean value pop-up
> window and click
> OK
> B. When prompted to choose the value for the new boolean, select true
> and click OK.
>
> 7. Rather than wait until a page has completely downloaded to display it
> to the user,
> Mozilla applications will regularly render what has been received to
> that point. This
> option controls the maximum amount of time the application will be
> unresponsive while
> rendering pages.
> Right-click (Apple users ctrl-click) anywhere in the about:config
> window, select New
> and then Integer from the pop-up menu.
> A. Enter content.max.tokenizing.time in the New integer value pop-up
> window and
> click OK
> B. You will be prompted to enter a value. Enter 2250000 and click OK.
>
> 8. CONTENT NOTIFY INTERVAL
> This option sets the minimum amount of time to wait between reflows.
> Right-click
> (Apple users ctrl-click) anywhere in the about:config window, select New
> and then
> Integer from the pop-up menu.
> A. Type content.notify.interval in the New integer value pop-up window
> and click OK.
> B. You will be prompted to enter a value. Enter 750000 and click OK.
>
> 9. CONTENT NOTIFY ONTIMER
> A. This option sets if to reflow pages at an interval any higher than
> that specified by
> content.notify.interval. Right-click (Apple users ctrl-click) anywhere
> in the
> about:config window and select New and then Boolean from the pop-up menu.
> B. Type content.notify.ontimer in the New boolean value pop-up window
> and click OK.
> C. You will be prompted to choose the value for the new boolean. Select
> true and click
> OK.
>
> 10. Notify Backoffcount
> This option controls the maximum number of times the content will do
> timer-based
> reflows. After this number has been reached, the page will only reflow
> once it is finished
> downloading. Right-click (Apple users ctrl-click) anywhere in the
> about:config window
> and select New and then Integer from the pop-up menu.
> A. Enter content.notify.backoffcount in the New integer value pop-up
> window and click
> OK.
> B. You will be prompted to enter a value. Enter 5 and click OK.
>
> 11. CONTENT SWITCH THRESHOLD
> You can interact with a loading page when content.interrupt.parsing is
> set to true.
> When a page is loading, the application has two modes: a high frequency
> interrupt mode
> and a low frequency interrupt mode. The first one interrupts the parser
> more frequently to
> allow for greater UI responsiveness during page load.
> The low frequency interrupt mode interrupts the parser less frequently
> to allow for
> quicker page load. The application enters high frequency interrupt mode
> when you move
> the mouse or type on the keyboard and switch back to low frequency mode
> when you had
> no activity for a certain amount of time. This preference controls that
> amount of time.
> Right-click (Apple users ctrl-click) anywhere in the about:config window
> and select
> New and then Integer from the pop-up menu.
> A. Enter content.switch.threshold in the New integer value pop-up window
> and click
> OK.
> B. You will be prompted to enter a value. Enter 750000 and click OK.
>
> 12. NGLAYOUT INITIALPAINT DELAY
> Mozilla applications render web pages incrementally, they display what’s
> been received
> of a page before the entire page has been downloaded. Since the start of
> a web page
> normally doesn’t have much useful information to display, Mozilla
> applications will wait
> a short interval before first rendering a page. This preference controls
> that interval. Rightclick
> (Apple users ctrl-click) anywhere in the about:config window and select
> New and
> then Integer from the pop-up menu.
> A. Enter nglayout.initialpaint.delay in the New integer value pop-up
> window and click
> OK.
> B. You will be prompted to enter a value. Enter 0 and click OK.

Thanks for the info. For whatever reason since I migrated to
roadrunner.com I can't get any of the _alt.*_ newgroups so your quote
helped me.

FF's layout must have changed because I found the *abouts* under Help in
FF. Most of the above sounds like the description of how Faster Fox works.
Did you get a chance to read its description? For the sake of bandwidth
I'll not quote it here but leave it for those interested to follow up on
the action differences.

Don

user@domain.invalid keyboarded, On 1/29/2008 11:42 AM :
> Don Nickell schreef:
>> user@domain.invalid wrote:
>>> I found on the internet a pdf file helping to double the speed of
>>> firefox.
>>>
>>> Is this really possible, and if so than why isn't it implemented
>>> standard in Firefox?
>>
>> Could you share this secret with all of us so we can enjoy the
>> benefits too? I'm using the FasterFox extension
>> (http://fasterfox.mozdev.org/) and it makes a noticeable difference.
>
>
> Ik copied the text from the PDF (which I downloaded from the newsgroup
> alt.binaries.e-book
> (The PDF also contained pictures)
>
> (Does anybody know if it works, and if so why isn't implemented
> standard in Firefox.)
>
> See for the text below.
>
>
> --------------------------------------
>
> Now here are some Tips&Tricks that can help you double the speed of
> Firefox.
>
> 1. Type about:config in the address bar and then press Enter.
>
> 2. In the filter search bar type network.http.pipelining. Be sure the
> value field is set
> true,if not double-click to set true.
> HTTP is the application-layer protocol that most web pages are
> transferred with. In
> HTTP 1.1, multiple requests can be sent before any responses are
> received. This is known
> as pipelining. Pipelining reduces page loading times, but not all
> servers support it.
>
> 3. Go back to the filter search bar and type
> network.http.pipelining.maxrequests.
> Double-click this option and set its value to 8.
>
> 4. In the filter search bar and type network.http.proxy.pipelining.
> Once opened doubleclick
> on it and set it to true.
>
> 5. In IPv6-capable DNS servers, an IPv4 address may be returned when
> an IPv6 address
> is requested. It is possible for Mozilla to recover from this
> misinformation, but a
> significant delay is introduced.
> Type network.dns.disableIPv6 in the filter search bar and set this
> option to true by
> double clicking on it.
>
> 6. CONTENT INTERRUPT PARSING
> This preference controls if the application will interrupt parsing a
> page to respond to UI
> events. It does not exist by default.
> Right-click (Apple users ctrl-click) anywhere in the about:config
> window, select New
> and then Boolean from the pop-up menu. Then:
> A. Enter content.interrupt.parsing in the New boolean value pop-up
> window and click
> OK
> B. When prompted to choose the value for the new boolean, select true
> and click OK.
>
> 7. Rather than wait until a page has completely downloaded to display
> it to the user,
> Mozilla applications will regularly render what has been received to
> that point. This
> option controls the maximum amount of time the application will be
> unresponsive while
> rendering pages.
> Right-click (Apple users ctrl-click) anywhere in the about:config
> window, select New
> and then Integer from the pop-up menu.
> A. Enter content.max.tokenizing.time in the New integer value pop-up
> window and
> click OK
> B. You will be prompted to enter a value. Enter 2250000 and click OK.
>
> 8. CONTENT NOTIFY INTERVAL
> This option sets the minimum amount of time to wait between reflows.
> Right-click
> (Apple users ctrl-click) anywhere in the about:config window, select
> New and then
> Integer from the pop-up menu.
> A. Type content.notify.interval in the New integer value pop-up window
> and click OK.
> B. You will be prompted to enter a value. Enter 750000 and click OK.
>
> 9. CONTENT NOTIFY ONTIMER
> A. This option sets if to reflow pages at an interval any higher than
> that specified by
> content.notify.interval. Right-click (Apple users ctrl-click) anywhere
> in the
> about:config window and select New and then Boolean from the pop-up menu.
> B. Type content.notify.ontimer in the New boolean value pop-up window
> and click OK.
> C. You will be prompted to choose the value for the new boolean.
> Select true and click
> OK.
>
> 10. Notify Backoffcount
> This option controls the maximum number of times the content will do
> timer-based
> reflows. After this number has been reached, the page will only reflow
> once it is finished
> downloading. Right-click (Apple users ctrl-click) anywhere in the
> about:config window
> and select New and then Integer from the pop-up menu.
> A. Enter content.notify.backoffcount in the New integer value pop-up
> window and click
> OK.
> B. You will be prompted to enter a value. Enter 5 and click OK.
>
> 11. CONTENT SWITCH THRESHOLD
> You can interact with a loading page when content.interrupt.parsing is
> set to true.
> When a page is loading, the application has two modes: a high
> frequency interrupt mode
> and a low frequency interrupt mode. The first one interrupts the
> parser more frequently to
> allow for greater UI responsiveness during page load.
> The low frequency interrupt mode interrupts the parser less frequently
> to allow for
> quicker page load. The application enters high frequency interrupt
> mode when you move
> the mouse or type on the keyboard and switch back to low frequency
> mode when you had
> no activity for a certain amount of time. This preference controls
> that amount of time.
> Right-click (Apple users ctrl-click) anywhere in the about:config
> window and select
> New and then Integer from the pop-up menu.
> A. Enter content.switch.threshold in the New integer value pop-up
> window and click
> OK.
> B. You will be prompted to enter a value. Enter 750000 and click OK.
>
> 12. NGLAYOUT INITIALPAINT DELAY
> Mozilla applications render web pages incrementally, they display
> what’s been received
> of a page before the entire page has been downloaded. Since the start
> of a web page
> normally doesn’t have much useful information to display, Mozilla
> applications will wait
> a short interval before first rendering a page. This preference
> controls that interval. Rightclick
> (Apple users ctrl-click) anywhere in the about:config window and
> select New and
> then Integer from the pop-up menu.
> A. Enter nglayout.initialpaint.delay in the New integer value pop-up
> window and click
> OK.
> B. You will be prompted to enter a value. Enter 0 and click OK.

To add to Don's comment, these edits of the configuration are
essentially what the Fasterfox add-on will do. They are not turned on
for at least two reasons. One, use of pipelining is highly dependent on
a high bandwidth connection which would not be filled to capacity with
the feature turned off. Secondly, the proportion of servers that have
pipelining support has been low, so a default of ON would be detrimental
to both dial-up and non-pipelining.

I would not view use of pipelining as speeding up Firefox, rather it a
technique to challenge the network connection to use it's full capacity
to treansport data in less time. Yes, the effect is it makes the
software look like it's faster when all the needed hardware support is
available.

--
Ron K.
Who is General Failure, and why is he searching my HDD?
Kernel Restore reported BSOD use by Major Error to msg the enemy!

Ron K. wrote:
>
> To add to Don's comment, these edits of the configuration are
> essentially what the Fasterfox add-on will do. They are not turned on
> for at least two reasons. One, use of pipelining is highly dependent on
> a high bandwidth connection which would not be filled to capacity with
> the feature turned off. Secondly, the proportion of servers that have
> pipelining support has been low, so a default of ON would be detrimental
> to both dial-up and non-pipelining.
>
> I would not view use of pipelining as speeding up Firefox, rather it a
> technique to challenge the network connection to use it's full capacity
> to treansport data in less time. Yes, the effect is it makes the
> software look like it's faster when all the needed hardware support is
> available.
>
Furthermore, if you are using Kaspersky Anti Virus or Kaspersky Internet
Security, you'll find that turning on pipelining prevents FF from
working correctly, with "hangs" on trying to open many web pages, etc.

--
Wilf

Wilf schreef:
> Ron K. wrote:
>>
>> To add to Don's comment, these edits of the configuration are
>> essentially what the Fasterfox add-on will do. They are not turned on
>> for at least two reasons. One, use of pipelining is highly dependent
>> on a high bandwidth connection which would not be filled to capacity
>> with the feature turned off. Secondly, the proportion of servers that
>> have pipelining support has been low, so a default of ON would be
>> detrimental to both dial-up and non-pipelining.
>>
>> I would not view use of pipelining as speeding up Firefox, rather it a
>> technique to challenge the network connection to use it's full
>> capacity to treansport data in less time. Yes, the effect is it makes
>> the software look like it's faster when all the needed hardware
>> support is available.
>>
> Furthermore, if you are using Kaspersky Anti Virus or Kaspersky Internet
> Security, you'll find that turning on pipelining prevents FF from
> working correctly, with "hangs" on trying to open many web pages, etc.
>
Is this typically a Kaspersky thing or do others like NOD32 give the same problems with FF pipelining.

user@domain.invalid wrote:
> Wilf schreef:
>> Ron K. wrote:
>>>
>>> To add to Don's comment, these edits of the configuration are
>>> essentially what the Fasterfox add-on will do. They are not turned
>>> on for at least two reasons. One, use of pipelining is highly
>>> dependent on a high bandwidth connection which would not be filled
>>> to capacity with the feature turned off. Secondly, the proportion of
>>> servers that have pipelining support has been low, so a default of
>>> ON would be detrimental to both dial-up and non-pipelining.
>>>
>>> I would not view use of pipelining as speeding up Firefox, rather it
>>> a technique to challenge the network connection to use it's full
>>> capacity to treansport data in less time. Yes, the effect is it
>>> makes the software look like it's faster when all the needed
>>> hardware support is available.
>>>
>> Furthermore, if you are using Kaspersky Anti Virus or Kaspersky
>> Internet Security, you'll find that turning on pipelining prevents
>> FF from working correctly, with "hangs" on trying to open many web
>> pages, etc.
>>
> Is this typically a Kaspersky thing or do others like NOD32 give the
> same problems with FF pipelining.
In Kaspersky this problem can be addressed by adding the (hanging) url
as a trusted site, settings/web anti-virus. I should imagine Nod32
should offer similar functionality but I have no experience of this
product.

However, overall I agree with Ron K and I avoid using pipelining but all
the other settings work fine for me.
Brian

Brian wrote, on 30/01/2008 11:34 pm:
> In Kaspersky this problem can be addressed by adding the (hanging) url
> as a trusted site, settings/web anti-virus. I should imagine Nod32
> should offer similar functionality but I have no experience of this
> product.
>
> However, overall I agree with Ron K and I avoid using pipelining but all
> the other settings work fine for me.

As it happens a lot with Kaspersky you don't want to make all sites
trusted! It's because of the way Kaspersky proxy's the ports, I'm told,
so not sure if the same would apply to NOD32 and others.

--
Wilf

On Or About Tue, 29 Jan 2008 14:09:36 +0100, Without Any Hesitation
Or Thinking Twice, user@domain.invalid Stumbled Over To The Keyboard
And wrote The Following In The mozilla.support.firefox News Group:

> I found on the internet a pdf file helping to double the speed of firefox.
>
> Is this really possible, and if so than why isn't it implemented standard in Firefox?

My version of Firefox out of the box is so damn fast I can barely
keep up with it.
--
Just West Of Nowhere
Enjoy Life And Live It To Its Fullest
http://www.NuBoy-Industries.Com
1/31/2008 7:26:21 AM CST

Wilf wrote:
> Brian wrote, on 30/01/2008 11:34 pm:
>> In Kaspersky this problem can be addressed by adding the (hanging) url
>> as a trusted site, settings/web anti-virus. I should imagine Nod32
>> should offer similar functionality but I have no experience of this
>> product.
>>
>> However, overall I agree with Ron K and I avoid using pipelining but
>> all the other settings work fine for me.
>
> As it happens a lot with Kaspersky you don't want to make all sites
> trusted! It's because of the way Kaspersky proxy's the ports, I'm told,
> so not sure if the same would apply to NOD32 and others.
>
Why not use pipelining? That speeds things up.

On 31.01.2008 19:24, CET - what odd quirk of fate caused EE to generate
the following:? :
> Wilf wrote:
>
>> Brian wrote, on 30/01/2008 11:34 pm:
>>
>>> In Kaspersky this problem can be addressed by adding the (hanging) url
>>> as a trusted site, settings/web anti-virus. I should imagine Nod32
>>> should offer similar functionality but I have no experience of this
>>> product.
>>>
>>> However, overall I agree with Ron K and I avoid using pipelining but
>>> all the other settings work fine for me.
>>>
>> As it happens a lot with Kaspersky you don't want to make all sites
>> trusted! It's because of the way Kaspersky proxy's the ports, I'm told,
>> so not sure if the same would apply to NOD32 and others.
>>
>>
> Why not use pipelining? That speeds things up.
>

very few webpages support pipelining - those that DON'T support it run
*slower* with pipelining activated!

reg

On Or About Thu, 31 Jan 2008 21:42:33 +0100, Without Any Hesitation
Or Thinking Twice, squaredancer Stumbled Over To The Keyboard And
wrote The Following In The mozilla.support.firefox News Group:

> On 31.01.2008 14:27, CET - what odd quirk of fate caused Old Gringo to
> generate the following:? :
>> On Or About Tue, 29 Jan 2008 14:09:36 +0100, Without Any Hesitation
>> Or Thinking Twice, user@domain.invalid Stumbled Over To The Keyboard
>> And wrote The Following In The mozilla.support.firefox News Group:
>>
>>
>>> I found on the internet a pdf file helping to double the speed of firefox.
>>>
>>> Is this really possible, and if so than why isn't it implemented standard in Firefox?
>>>
>>
>> My version of Firefox out of the box is so damn fast I can barely
>> keep up with it.
>>
>
> ..... and, I bet your keyboard is (at least) twice as fast as your fingers!
>
> reg

LMAO You got that right, and the damn thing can not spell.
--
Just West Of Nowhere
Enjoy Life And Live It To Its Fullest
http://www.NuBoy-Industries.Com
1/31/2008 9:18:50 PM CST

squaredancer wrote:
> On 31.01.2008 19:24, CET - what odd quirk of fate caused EE to generate
> the following:? :
>> Wilf wrote:
>>
>>> Brian wrote, on 30/01/2008 11:34 pm:
>>>
>>>> In Kaspersky this problem can be addressed by adding the (hanging)
>>>> url as a trusted site, settings/web anti-virus. I should imagine
>>>> Nod32 should offer similar functionality but I have no experience of
>>>> this product.
>>>>
>>>> However, overall I agree with Ron K and I avoid using pipelining but
>>>> all the other settings work fine for me.
>>>>
>>> As it happens a lot with Kaspersky you don't want to make all sites
>>> trusted! It's because of the way Kaspersky proxy's the ports, I'm
>>> told, so not sure if the same would apply to NOD32 and others.
>>>
>>>
>> Why not use pipelining? That speeds things up.
>>
>
> very few webpages support pipelining - those that DON'T support it run
> *slower* with pipelining activated!

No only slower, but some go on an "indefinite download loop" ... where
the page appears to never complete downloading.
example page for me was: http://www.filehippo.com/
(the problem was solved the moment I switched pipelining off)

kes wrote:
> squaredancer wrote:
>> On 31.01.2008 19:24, CET - what odd quirk of fate caused EE to
>> generate the following:? :
>>> Wilf wrote:
>>>
>>>> Brian wrote, on 30/01/2008 11:34 pm:
>>>>
>>>>> In Kaspersky this problem can be addressed by adding the (hanging)
>>>>> url as a trusted site, settings/web anti-virus. I should imagine
>>>>> Nod32 should offer similar functionality but I have no experience
>>>>> of this product.
>>>>>
>>>>> However, overall I agree with Ron K and I avoid using pipelining
>>>>> but all the other settings work fine for me.
>>>>>
>>>> As it happens a lot with Kaspersky you don't want to make all sites
>>>> trusted! It's because of the way Kaspersky proxy's the ports, I'm
>>>> told, so not sure if the same would apply to NOD32 and others.
>>>>
>>>>
>>> Why not use pipelining? That speeds things up.
>>>
>>
>> very few webpages support pipelining - those that DON'T support it run
>> *slower* with pipelining activated!
>
> No only slower, but some go on an "indefinite download loop" ... where
> the page appears to never complete downloading.
> example page for me was: http://www.filehippo.com/
> (the problem was solved the moment I switched pipelining off)

Other sites, such as Google Maps load much slower, if at all, with
pipelining.


--
Ron Hunter rphunter@charter.net

Ron Hunter has written on 2/1/2008 2:54 PM:
> Other sites, such as Google Maps load much slower, if at all, with
> pipelining.

GMaps is not noticeably slower here.

--
Pete Holsberg
Columbus, NJ

Senility Prayer
God grant me the senility to forget the people I never liked anyway, the
good fortune to run into the ones that I do, and the eyesight to tell
the difference.

On 2/1/2008 11:31 AM, EE wrote:
> kes wrote:
>> squaredancer wrote:
>>> On 31.01.2008 19:24, CET - what odd quirk of fate caused EE to
>>> generate the following:? :
>>>> Wilf wrote:
>>>>
>>>>> Brian wrote, on 30/01/2008 11:34 pm:
>>>>>
>>>>>> In Kaspersky this problem can be addressed by adding the (hanging)
>>>>>> url as a trusted site, settings/web anti-virus. I should imagine
>>>>>> Nod32 should offer similar functionality but I have no experience
>>>>>> of this product.
>>>>>>
>>>>>> However, overall I agree with Ron K and I avoid using pipelining
>>>>>> but all the other settings work fine for me.
>>>>>>
>>>>> As it happens a lot with Kaspersky you don't want to make all sites
>>>>> trusted! It's because of the way Kaspersky proxy's the ports, I'm
>>>>> told, so not sure if the same would apply to NOD32 and others.
>>>>>
>>>>>
>>>> Why not use pipelining? That speeds things up.
>>>>
>>>
>>> very few webpages support pipelining - those that DON'T support it
>>> run *slower* with pipelining activated!
>>
>> No only slower, but some go on an "indefinite download loop" ...
>> where the page appears to never complete downloading.
>> example page for me was: http://www.filehippo.com/
>> (the problem was solved the moment I switched pipelining off)
>
> I just tried that page. It loaded fine for me. I have been using
> pipelining with both browser and filtering proxy for years, and am not
> having problems. I did have problems when I tried to use a filtering
> proxy that did not support pipelining. It was way too slow.

FF2.0.0.11 on win XP SP2. Almost instantaneous with pipelining enabled!

--
Irwin

Please do not use my email address to make requests for help.
Knowledge Base: http://kb.mozillazine.org/Main_Page

On 2/1/2008 11:54 AM, Ron Hunter wrote:
> kes wrote:
>> squaredancer wrote:
>>> On 31.01.2008 19:24, CET - what odd quirk of fate caused EE to
>>> generate the following:? :
>>>> Wilf wrote:
>>>>
>>>>> Brian wrote, on 30/01/2008 11:34 pm:
>>>>>
>>>>>> In Kaspersky this problem can be addressed by adding the (hanging)
>>>>>> url as a trusted site, settings/web anti-virus. I should imagine
>>>>>> Nod32 should offer similar functionality but I have no experience
>>>>>> of this product.
>>>>>>
>>>>>> However, overall I agree with Ron K and I avoid using pipelining
>>>>>> but all the other settings work fine for me.
>>>>>>
>>>>> As it happens a lot with Kaspersky you don't want to make all sites
>>>>> trusted! It's because of the way Kaspersky proxy's the ports, I'm
>>>>> told, so not sure if the same would apply to NOD32 and others.
>>>>>
>>>>>
>>>> Why not use pipelining? That speeds things up.
>>>>
>>>
>>> very few webpages support pipelining - those that DON'T support it
>>> run *slower* with pipelining activated!
>>
>> No only slower, but some go on an "indefinite download loop" ...
>> where the page appears to never complete downloading.
>> example page for me was: http://www.filehippo.com/
>> (the problem was solved the moment I switched pipelining off)
>
> Other sites, such as Google Maps load much slower, if at all, with
> pipelining.
>
>
I don't experience any slowdown w/Google maps with pipelining enabled.

--
Irwin

Please do not use my email address to make requests for help.
Knowledge Base: http://kb.mozillazine.org/Main_Page

Pete Holsberg wrote:
> Ron Hunter has written on 2/1/2008 2:54 PM:
>> Other sites, such as Google Maps load much slower, if at all, with
>> pipelining.
>
> GMaps is not noticeably slower here.
>
Much depends on the routing, and total time in the path. The longer it
is, the more likely pipelining is to fail.

--
Ron Hunter rphunter@charter.net

Irwin Greenwald wrote:
> On 2/1/2008 11:54 AM, Ron Hunter wrote:
>> kes wrote:
>>> squaredancer wrote:
>>>> On 31.01.2008 19:24, CET - what odd quirk of fate caused EE to
>>>> generate the following:? :
>>>>> Wilf wrote:
>>>>>
>>>>>> Brian wrote, on 30/01/2008 11:34 pm:
>>>>>>
>>>>>>> In Kaspersky this problem can be addressed by adding the
>>>>>>> (hanging) url as a trusted site, settings/web anti-virus. I
>>>>>>> should imagine Nod32 should offer similar functionality but I
>>>>>>> have no experience of this product.
>>>>>>>
>>>>>>> However, overall I agree with Ron K and I avoid using pipelining
>>>>>>> but all the other settings work fine for me.
>>>>>>>
>>>>>> As it happens a lot with Kaspersky you don't want to make all
>>>>>> sites trusted! It's because of the way Kaspersky proxy's the
>>>>>> ports, I'm told, so not sure if the same would apply to NOD32 and
>>>>>> others.
>>>>>>
>>>>>>
>>>>> Why not use pipelining? That speeds things up.
>>>>>
>>>>
>>>> very few webpages support pipelining - those that DON'T support it
>>>> run *slower* with pipelining activated!
>>>
>>> No only slower, but some go on an "indefinite download loop" ...
>>> where the page appears to never complete downloading.
>>> example page for me was: http://www.filehippo.com/
>>> (the problem was solved the moment I switched pipelining off)
>>
>> Other sites, such as Google Maps load much slower, if at all, with
>> pipelining.
>>
>>
> I don't experience any slowdown w/Google maps with pipelining enabled.
>

I haven't tried to use it with pipelining lately, but when I first tried
the feature, I found a lot of sites I visited were much faster with it,
and some others were much slower. I turned it off, and haven't tried it
again in a couple of years. If the servers used at a site have been
upgraded to support pipelining, then they will be faster, but if not,
the slowdown can render response slower than dialup.
I may retry pipelining to see how it goes now. Still, with a reliable
5Mbps connection, pipelining really isn't necessary.


--
Ron Hunter rphunter@charter.net