- WATERFOX REVIEW 2015 HOW TO
- WATERFOX REVIEW 2015 32 BIT
- WATERFOX REVIEW 2015 SOFTWARE
- WATERFOX REVIEW 2015 WINDOWS
But several hundred? Again, I simply ask 'why'? Eventually you run out, no matter what the application. That is very much of an outlier case.Įach open tab consumes resources. But the OP (or you) says he needs to have several hundred tabs open at once, asking "why" is a valid question. I get that people have wildly different use cases. Customer says "I need to do X, and it needs to do it like this."ĩ5% of the time, I can come back with "Here is a faster/cheaper/easier way to get the results you are looking for." I would say - try it!Īs a developer, my job is to ask why.
WATERFOX REVIEW 2015 WINDOWS
But I don't know if Windows will allow that to happen, or if indeed Firefox can actually be 'tricked' into segregating itself into completely separate 'programs' which call their own RAM reserves from the system pool.
WATERFOX REVIEW 2015 HOW TO
As a solution, assuming you don't use PaleMoon which I've never used, you might consider, (I have no idea if this works) opening MULTIPLE INSTANCES of Firefox (not just opening new windows - see the Mozilla page for how to open a new instance with a new user profile) this MAY (MAY!) bypass the RAM limit on each Firefox instance, allowing you to feed each instance a full bloc of RAM, and possibly avoiding all the aforementioned issues. Also note that you cannot use Firefox AND Waterfox at the same time they block each other.Ħ. It actually led to it being a problem, and so I'm waiting for them to correct this. Finally - I happen to know that the current release of Waterfox has a weird quirk/bug which has nothing to do with RAM, and while the program works fine (as it always has), it tends to spike on CPU usage (this has been noted I believe on the dev page) for some reason that I can't figure out. Java threads, flash instances, the program's own plugin container, the OS/program memory management (infamously problematic in ALL browsers, Chrome/Safari/Opera/IE/Firefox, etc.), and a few other things I'm not well versed in, all WILL affect how the program performs, regardless of RAM availability.ĥ.
WATERFOX REVIEW 2015 SOFTWARE
Many elements of the program's software architecture come into play in this problem - simply increasing the RAM availability then, simply won't be able to compensate for performance degradation that is actually a fundamental architecture problem. The reason is actually very simple: The program (most programs for that matter) doesn't simply scale linearly with more memory - it's not as if each 'tab' uses a certain amount of RAM and that by simply increasing RAM usage you can therefore maintain the same program stability/performance that you would see if you were using it more in line with its design specs (which, I suspect, are probably something like <250tabs open, ceteris paribus). However, whether this will allow the stable running of so many tabs - more than say, a few hundred, I'm very suspect about. As to answering the OP's actual question - YES Waterfox will be able to use more of your RAM, and won't be limited to the 2GB or so that I believe Firefox instances tend to clock out at.
I suspect anyone saying this just doesn't know anything about Waterfox, or similar browsers (e.g. are very unfounded it has a fairly active userbase, and indeed, there are those that claim that IE is susceptible enough to to malware to qualify as 'having a virus' just by using it. The concerns of Waterfox having "viruses" etc. The reasons I do that aren't really relevant either.ģ. I see absolutely no reason why OP shouldn't be able to open 3000 tabs if he/she so desired, so I'm not sure that just because his usage case is foreign to you, means that it's not a valid question - it is I myself tend to do a combination of 4 different browsers open at the same time, bookmarking tabs I close, or suspending them using a few suspension addons, but I'd say I have a few hundred open across the browsers at any given instant in time.
WATERFOX REVIEW 2015 32 BIT
The main advantage of 64bit programs (any programs) is that they are able to use more memory (more then 3 or 4GB depending on who you ask/how you think about it) than the implicit register limit imposed by 32 bit programs, like Firefox.Ģ. Waterfox is the 64bit version of Firefox built and maintained by a separate community independent of Mozilla. This has been a fairly clueless discussion:ġ.
0 kommentar(er)
