With Firefox 33.0 I get 28 fps with 2000 and 18 fps with 4000. Much slower with then Chrome.
With Firefox 33.0 I get 28 fps with 2000 and 18 fps with 4000. Much slower with then Chrome.
Information on my Main laptop. Information on my small laptop Dell 11 3000
Using a Asus 3632QM laptop with 8gig RAM, 250 SSD.
Machine Registered 366271, 366273, 366275.
Registered Ubuntu user number 18630. Registered Linux user number 458093.
To be fair Chrome nor Midori even ran the WebGL plugin for me. I've been trying to move away from FireFox.
You know what's interesting me? My laptop got 10 FPS despite displaying two screens in Xinerama mode and having a mobility Radeon HD 3100 right? Well my desktop has a HD 3300 integrated GPU and is just a single display, but it only got 7 FPS. Meanwhile the dispaly on the laptop didn't look visually as smooth as on the desktop?! O.o
One difference is I'm just using the open source "radeon" driver on the desktop but the proprietary drivers on the laptop.
I use Chrome v39. On my laptop I get ~60 fps at 1000, ~40 fps at 2000, and ~30 fps at 4000. Whatever that means.
With Firefox 33, I get 8 fps no matter what I select.
Last edited by Old_Grey_Wolf; December 2nd, 2014 at 10:35 PM.
Use whatever OS or desktop works for you. Dual boot or use VMs if you want. Backup your computer regularly, and definitely before upgrading, partitioning, or installing an OS.
No support requests by PM please.
Firefox 33.0 gets 60fps at 4k with GeForce GTX 750 Ti graphics running nvidia 343.22 and no other browser tabs.
Youtube vids do not like sharing FF with plenty of fish. 8 tabs drops to around 40 fps.
Enjoyed fiddling the advanced options, speaking as a non-gamer.
Chrome: Stable 60fps at 4000 fish.
Using a GeForce GTX780ti card.
The WebGL uses hardware acceleration. From the Wiki page it said "code that is executed on a computer's Graphics Processing Unit (GPU)" and I did notice that if I let it run for, say 5 to 10 minutes, it does heat up the GPU and the fan kicks on and and starts blowing out the heat. This means that there are some factors in the fps on graphics. One being the browser and the other being the GPU speed.
It sounds like this is done by code within JavaScript.
Information on my Main laptop. Information on my small laptop Dell 11 3000
Using a Asus 3632QM laptop with 8gig RAM, 250 SSD.
Machine Registered 366271, 366273, 366275.
Registered Ubuntu user number 18630. Registered Linux user number 458093.
Only got to try out the 50 fish setting ....
Both google-chrome-stable and chromium on Debian Wheezy give the error grahammechanical noted earlier.
Firefox Nightly, 1 fps then the browser seizes solid requiring a kill signal.
Iceweasel (Debian branded firefox), similar to Nightly without seizing (a painful 1fps)
It doesn't here, the next quote box from this install may give a clue whyhow does your hardware/software stack up?
On an old HP dv6 dual core laptop. Can't even use VDPAU acceleration with mplayer on this old "pile of junk"01:00.0 VGA compatible controller: NVIDIA Corporation G72M [GeForce Go 7400] (rev a1)
I really need to get off my big butt and fix my desktop tower.
48 fps with 100 fish.
37 fps with 1000 fish.
21 fps with 4000 fishies.
Not really ground braking but a nice test!
Used firefox 34 and intel gpu.
Last edited by xubu2; December 7th, 2014 at 03:54 AM.
My result is pathetic. 1fps @50 fishes.
AMD 64 X2 5600+
Ram : 2GB
Nvidia 6150 SE (Non free driver)
Firefox 34.0.5
Lubuntu 20.04
4000 fish at 60 fps in Chrome.
4000 fish at 15 fps in FF.
Please read The Forum Rules and The Forum Posting Guidelines
A thing discovered and kept to oneself must be discovered time and again by others. A thing discovered and shared with others need be discovered only the once.
This universe is crazy. I'm going back to my own.
Bookmarks