Overclock.net › Forums › Software, Programming and Coding › Other Software › Waterfox 48.0.2: 06 September [Firefox 64-Bit]
New Posts  All Forums:Forum Nav:

Waterfox 48.0.2: 06 September [Firefox 64-Bit] - Page 266

post #2651 of 7225
Tabs work fine for me. Waterfox 13 PL1 is working fine for me, other than the protected mode Flash issue now and then but I'm waiting for Adobe to issue a fix for that one.
The Batcomputer
(24 items)
 
  
CPUMotherboardGraphicsGraphics
Intel Core i7-6700K @ 4.6 GHz ASUS Z170-PREMIUM LGA 1151 ATX Intel Motherboard ASUS ROG GeForce GTX 1070 STRIX-GTX1070-O8G-GAM... ASUS ROG GeForce GTX 1070 STRIX-GTX1070-O8G-GAM... 
RAMHard DriveHard DriveHard Drive
G.SKILL Trident Z Series 32GB (2 x 16GB) 3200MH... SAMSUNG 950 PRO M.2 256GB SSD (Windows) SAMSUNG 840 PRO 128GB SATA III SSD (macOS) SAMSUNG 850 PRO 128GB SATA III SSD (Ubuntu) 
Hard DriveHard DriveHard DriveHard Drive
SAMSUNG 850 EVO 500GB SATA III SSD (Games + Vir... Seagate Ironwolf 10TB NAS 7200 RPM 256MB Cache ... Seagate Ironwolf 10TB NAS 7200 RPM 256MB Cache ... Seagate Ironwolf 10TB NAS 7200 RPM 256MB Cache ... 
CoolingOSOSOS
Swiftech H320-X2 Prestige AIO Water Cooling Windows 10 Pro Anniversary Update 64-bit macOS 10.12 Sierra Ubuntu 16.04.1 Xenial Xerus 64-bit 
MonitorKeyboardPowerCase
QNIX QX2710 LED Evolution ll 27" 2560x1440 WQHD... Ducky Shine 5 RGB LED Backlit Mechanical Keyboa... EVGA Supernova 1200 P2 80 PLUS PLATINUM Certifi... Phanteks Enthoo Primo ATX Full Tower Computer C... 
MouseMouse PadAudioAudio
Ducky Secret RGB Mouse Ducky Flipper Mouse Pad Schiit Modi 2 Uber USB DAC Behringer MS40 Studio Monitors 
  hide details  
Reply
The Batcomputer
(24 items)
 
  
CPUMotherboardGraphicsGraphics
Intel Core i7-6700K @ 4.6 GHz ASUS Z170-PREMIUM LGA 1151 ATX Intel Motherboard ASUS ROG GeForce GTX 1070 STRIX-GTX1070-O8G-GAM... ASUS ROG GeForce GTX 1070 STRIX-GTX1070-O8G-GAM... 
RAMHard DriveHard DriveHard Drive
G.SKILL Trident Z Series 32GB (2 x 16GB) 3200MH... SAMSUNG 950 PRO M.2 256GB SSD (Windows) SAMSUNG 840 PRO 128GB SATA III SSD (macOS) SAMSUNG 850 PRO 128GB SATA III SSD (Ubuntu) 
Hard DriveHard DriveHard DriveHard Drive
SAMSUNG 850 EVO 500GB SATA III SSD (Games + Vir... Seagate Ironwolf 10TB NAS 7200 RPM 256MB Cache ... Seagate Ironwolf 10TB NAS 7200 RPM 256MB Cache ... Seagate Ironwolf 10TB NAS 7200 RPM 256MB Cache ... 
CoolingOSOSOS
Swiftech H320-X2 Prestige AIO Water Cooling Windows 10 Pro Anniversary Update 64-bit macOS 10.12 Sierra Ubuntu 16.04.1 Xenial Xerus 64-bit 
MonitorKeyboardPowerCase
QNIX QX2710 LED Evolution ll 27" 2560x1440 WQHD... Ducky Shine 5 RGB LED Backlit Mechanical Keyboa... EVGA Supernova 1200 P2 80 PLUS PLATINUM Certifi... Phanteks Enthoo Primo ATX Full Tower Computer C... 
MouseMouse PadAudioAudio
Ducky Secret RGB Mouse Ducky Flipper Mouse Pad Schiit Modi 2 Uber USB DAC Behringer MS40 Studio Monitors 
  hide details  
Reply
post #2652 of 7225
Quote:
Originally Posted by TheHunter View Post

Thanks,
so the best effect is to set
content.notify.interval: to 1 sec (1000000)
then i need content.max.tokenizing.time: 3.6sec (3600000), Isn't that a bit high compared to 360ms?
edit: i 've set it like so (1sec; 3.6sec) and it looks good, i also disabled initial paint delay to 0ms and it looks snappy, youtube videos are ok too smile.gif
edit2: content.max.tokenizing.time: 3.6sec (3600000) lagged animated looped gifs, setting it back to 360ms fixed it.

The content.notify.interval doesn't need to be that high. Since the default is 120000, you can try going up to maybe 300000 then maybe 500000 to see if it helps to smooth everything out. Here's a better description of the setting:

content.notify.interval [Integer] *Create - Note that for this setting to work, a new Boolean called content.notify.ontimer must also be created and set to True as well. The value in microseconds for this preference (where 1000 microseconds = 1 millisecond = 1/1000th of a second) determines how long Firefox buffers network data before displaying it. By default this is 120000 microseconds (120 milliseconds). Lowering this setting may improve display speed in Firefox, however it will also increase CPU usage to do so. Experiment with this setting, either raising it or lowering it to see if the results are beneficial on your system. Don't drop this value to one which is extremely low however. If in doubt, do not change this value as you are more likely to slow Firefox down than speed it up.

The content.max.tokenizing.time is not as important or optional but can make a difference when combined with the other setting. It should be a multiple of 3x what the content.notify.interval is. So if content.notify.interval is set to 200000, then content.max.tokenizing.time would be 600000. Whatever the multiple is for content.max.tokenizing.time, you can then start lowering that number by maybe 50000. Lowering the interval will make the application more responsive at the expense of page load time. Like I said, this setting isn't as important but here's what it does:

This preference controls the maximum amount of time the application will be unresponsive while rendering pages.
Edited by djkilla - 6/13/12 at 7:47pm
post #2653 of 7225
Quote:
Originally Posted by djkilla View Post

Most of those tweaks I've included. This is an add-on which lets you tweak the settings without manually using about:config. It's not a bad add-on. It lets you do changes quickly and might be perfect for you to try to see if it improves or solve the YouTube jittering issue. If you get it, I would recommend changing the settings under 'Paint & Rendering'. Those settings control the page reflow which could be causing the jittering in YouTube. You can try increasing the numbers. This will cause Waterfox to not reflow the page as often.
Now that I think about it, you may want to try changing my tweak to reduce the amount of RAM Firefox uses for its cache feature from 0 to -1
1. Type “about:config” (no quotes) in the adress bar in the browser.
2. Find “browser.sessionhistory.max_total_viewer”
3. Set it’s value to “-1“
'0' keeps everything from being cached to RAM. But if you're streaming a YouTube video, you may need this setting to be '-1' so the video will play smoother by caching/buffering the video to RAM. You may notice more memory/RAM being used to do this to get smoother video play. When I get time, I'll see if there's another way to reduce the RAM used by Waterfox.

Ok. I want to do it manually though smile.gif

Regadring the 10Mb RAM usage when minimized, why doesn't it work for me as I've said?
post #2654 of 7225
Why does fx 32 start faster than this?

Surfing I can definately see that Waterfox is faster, but shouldnt it start faster also?
post #2655 of 7225
Quote:
Originally Posted by kevindd992002 View Post

Ok. I want to do it manually though smile.gif
Regadring the 10Mb RAM usage when minimized, why doesn't it work for me as I've said?

There's actually two different settings to deal with. Here's a better description of config.trim_on_minimize:

On Windows operating systems, when a program is minimized and left for a period of time, Windows will swap memory the program is using from RAM onto the hard disk in anticipation that other programs might need RAM. Because of the way Mozilla applications are stored in memory, Windows is much more aggressive in swapping out the memory they use, which can cause a delay when the program is restored. This preference determines whether to allow Windows to swap out memory from a minimized Mozilla application.

When setting this to 'True', you'll be able to reduce the amount of RAM used but it may not be right away. When you minimize Firefox or leave it running without messing with it, Windows will swap out the memory Firefox is using. Windows overall controls everything but this setting allows the memory being used by Firefox to be swapped out when the above conditions exist.

browser.sessionhistory.max_total_viewer should have an 's' at the end. So the correct command/setting should be browser.sessionhistory.max_total_viewers Here's a better description for the setting:

browser.sessionhistory.max_total_viewers [Integer] - This option determines how many pages to store in memory to speed up the back and forward buttons in Firefox. The default of -1 automatically determines the amount based on your system RAM, and is generally recommended. At 512MB of RAM, 5 pages are held in memory, while 1GB or more of RAM holds 8 pages. You can set this value to 0 to hold no pages in RAM (only recommended for very low RAM or troubleshooting purposes), or increase the value if you often use the back and forward functions for more than 8 pages.

So these two settings will control the amount of ram used by Firefox/Waterfox. I recommended changing the browser.sessionhistory.max_total_viewers from '0' (Do not store any pages in memory.) to '-1' (Automatically determine the maximum amount of pages to store in memory based on the total amount of RAM (Default)). You'll use more memory with this setting but it may solve the jittering in YouTube videos by caching/buffering the video into memory while streaming it. You can also use positive integers to control the amount of RAM used. Take a look at the following page for additional info:

http://kb.mozillazine.org/Browser.sessionhistory.max_total_viewers
post #2656 of 7225
Quote:
Originally Posted by Conditioned View Post

Why does fx 32 start faster than this?
Surfing I can definately see that Waterfox is faster, but shouldnt it start faster also?

It's a combination of the Firefox code and how the code was compiled. Waterfox is always being improved in this area so how the code is compiled will change from time to time with each version. There's new versions of compilers coming out soon so Waterfox will continue to improve in this area. Once running, Waterfox is a speed beast when surfing the internet. biggrin.gif
post #2657 of 7225
Been using this over a week now, I actually posted a thread in the news section regarding the most recent update. XD

Haven't experienced any abnormal issues so far. Cheers.
post #2658 of 7225
Quote:
Originally Posted by djkilla View Post

There's actually two different settings to deal with. Here's a better description of config.trim_on_minimize:
On Windows operating systems, when a program is minimized and left for a period of time, Windows will swap memory the program is using from RAM onto the hard disk in anticipation that other programs might need RAM. Because of the way Mozilla applications are stored in memory, Windows is much more aggressive in swapping out the memory they use, which can cause a delay when the program is restored. This preference determines whether to allow Windows to swap out memory from a minimized Mozilla application.
When setting this to 'True', you'll be able to reduce the amount of RAM used but it may not be right away. When you minimize Firefox or leave it running without messing with it, Windows will swap out the memory Firefox is using. Windows overall controls everything but this setting allows the memory being used by Firefox to be swapped out when the above conditions exist.
browser.sessionhistory.max_total_viewer should have an 's' at the end. So the correct command/setting should be browser.sessionhistory.max_total_viewers Here's a better description for the setting:
browser.sessionhistory.max_total_viewers [Integer] - This option determines how many pages to store in memory to speed up the back and forward buttons in Firefox. The default of -1 automatically determines the amount based on your system RAM, and is generally recommended. At 512MB of RAM, 5 pages are held in memory, while 1GB or more of RAM holds 8 pages. You can set this value to 0 to hold no pages in RAM (only recommended for very low RAM or troubleshooting purposes), or increase the value if you often use the back and forward functions for more than 8 pages.
So these two settings will control the amount of ram used by Firefox/Waterfox. I recommended changing the browser.sessionhistory.max_total_viewers from '0' (Do not store any pages in memory.) to '-1' (Automatically determine the maximum amount of pages to store in memory based on the total amount of RAM (Default)). You'll use more memory with this setting but it may solve the jittering in YouTube videos by caching/buffering the video into memory while streaming it. You can also use positive integers to control the amount of RAM used. Take a look at the following page for additional info:
http://kb.mozillazine.org/Browser.sessionhistory.max_total_viewers

Thanks. But I left WF running overnight and the RAM usage is still high and unchanged even though I set config.trim_on_minimize to True. So Windows is the culprit here?

I remember that the first step in your list of tweaks is browser.sessionhistory.max_total_viewers but you were recommending a value of '0' there, can you modify the list for me to reflect a value of '-1' is better? Thanks.
post #2659 of 7225
Quote:
Originally Posted by kevindd992002 View Post

Thanks. But I left WF running overnight and the RAM usage is still high and unchanged even though I set config.trim_on_minimize to True. So Windows is the culprit here?
I remember that the first step in your list of tweaks is browser.sessionhistory.max_total_viewers but you were recommending a value of '0' there, can you modify the list for me to reflect a value of '-1' is better? Thanks.

Yea, Windows is to blame. Even though the setting is 'True', It's Windows that chooses how it controls everything. For browser.sessionhistory.max_total_viewers, I'll change the setting back to it's default of '-1' because this may help for streaming videos to run more smoothly. Otherwise, I prefer to use '0' to save memory and keep pages from being cached that I may not want to visit again. It's really a personal choice for the user and there's lots of choices to choose from for this setting to better manage the memory/cache.
post #2660 of 7225
Java plugin crashed after Java upgrade from ver 6 31 to 6 33. Anyone has the same problem with WF 13 PL1?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Other Software
Overclock.net › Forums › Software, Programming and Coding › Other Software › Waterfox 48.0.2: 06 September [Firefox 64-Bit]