(04-22-2015, 08:32 PM)SwagBunny Wrote: Chrome seems least demanding in the terms of CPU usage.
Yeah, also on a sidenote: Chrome is faster at simply anything and better. I don't know what you guys are doing all day long with your '50 tabs'. There is no real use for them at least for me and alike 75 % of the people around, I doubt you are able to work with 50 tabs simultaneously. And hey, heads up. There are addons for Chrome & this thing,.. so called... hm... 'bookmarks'/'retrieve' and 'recall' for chrome to store tabs without wasting any of your precious memory.
Here is an example, of a chrome addon you would like to use while having 50 tabs+ open ; ( https://chrome.google.com/webstore/detai...hhppkpkmkl ) I prefer using this instead of the group thingy in firefox, this just looks better and well, it's chrome <|3
Plugin Description Wrote:...However, the bad observability is not the worst problem; a much bigger problem is that all of these open tabs consume A LOT of RAM and CPU (plus often NETWORK BANDWIDTH) resources of a PC — sometimes, ALL OF THEM! I have a six core PC with 16GB of RAM, and in the past most of these resources were constantly consumed by open tabs. Now, with the help of this extension, it really feels like an absolutely new PC from a new era! No SSD, additional 10 CPU cores, or 100GB of RAM will give you this feeling if you happen to have the habit of leaving tabs open continually. In time, they tend to consume all available resources, and for some of us, it’s a very severe problem that this extension will solve...
I tend to say 'google is your friend', and your closest friend to solve this common memory problem with chrome, would be the addon shown above. So yeah guys, you should read into chrome & it's possibilities, there is always a solution...
Chrome doesn't do 1200 tabs, eleven windows or the plugins I need, but it does indeed do the rest rather well so I normally use both with Chrome for YT/Twitch/GDocs and Firefox for the rest depending on context. They are good at different things, and both (or perhaps all) browsers have their upsides and downsides for your not-so-average user with more than a few tabs open.
Re: Performance issues; the shine animation slowdown issue was not really an hardware issue, but rather a known and unresolved Firefox issue that has apparently been around in one form or another for four years or so where scrolling/resizing the viewport with certain animations or gradients visible will cause (very) noticeable performance drops.
EDIT:
(04-22-2015, 06:30 PM)Bloxin Wrote:
(04-22-2015, 05:35 PM)Error Wrote: EDIT: I suppose you could use a 1px tall gif with the animation as a replacement for Firefox/IE if you absolutely want the animation in all browsers, or some other workaround. IE11 doesn't even give it a try; it has rather poor support for CSS3 animations overall.
Well I don't think thats the case, as its fine now and I've like 50 tabs opened
Quick clarification: What I meant by that wasn't that IE11 was slow while showing the animation, but rather that IE11 doesn't support CSS3 animations very well yet - at least not without certain workarounds - so you wouldn't see it in the first place.
Odd, I've had zero problems with Firefox and this forum in recent times.
Another thing is, Firefox has literally only just released another update, FF is now at version 37.0.2!
As for having a zillion tags open..... 4 or 5 at the most if I have that many open.
Mostly when I am chasing something down on Goooogle and have found several different sources of info (possibly useful) that I want to look at.
The only time I seem to have problems is when playing browser games and then I suspect it is the game causing the problem, as a lot of games don't 'clean' the browser memory when they change between scenes and the ram slowly fills up. Bushwacker 2 is terrible for that. lol
(04-23-2015, 04:37 PM)Mickk Wrote: As for having a zillion tags open..... 4 or 5 at the most if I have that many open.
Well some of us are just better at multitasking I guess.
Also quite a few of us have slow or data capped connections (or both ) and we would rather keep tabs in ram then have to spend time reloading pages again.