Wolfgang wrote:
On Fri, 2004-03-12 at 00:45, Michal Zeravik wrote:
The speed of Flash movies It not depends on computer so much. When I run the yeti game, there is almost none processor activity for that process (from 'top'). Problem must be somewhere else. My machine is athlonxp2200+, gf4, 512DDR.
michal
Wolfgang wrote:
On Thu, 2004-03-11 at 02:29, Rotariu Bogdan wrote:
slow to me... running on a celeron 1700MHz / 512 DDR (fc1 with kernel 2.6.3)
On Wed, 2004-03-10 at 15:55, Wolfgang wrote:
On Thu, 2004-03-11 at 00:38, Mark Guzzo wrote:
Hello all,
My co-worker and I love to duke it out about Linux -vs- Windows. Yesterday he send me a flash link that I find quite funny.
http://home.tele2.fr/kcv/pinguin.swf
TUX can take a beating but he keeps on ticking :-)
Anyway..... When I play it on my FC1 box, it is very slow. I have to drop the quality down just to make it playable. But on his Windows box it run fine. I have seen this before with other *.swf files, so at least I know it's not particular to this site.
Does anyone else have the same issue?
I'm running on a P3 with 512M.
Mark
Seems to be ok to me... But then I'm running a somewhat faster system.
Wolf
PS. Cool little game... Damn addictive. :-)
I have not noticed it being slow due to my system being a Dual Athlon MP2800+ CPU's, 1.5GB of REG RAM and a MSI GeForce FX 5950 Ultra video card.
Wolf
What Video Drivers are you running??? I'm running Nvidia's latest V53.36 drivers. And all seems to run ok. Even OpenGL Games run fast.
Wolf
Folks:
Perhaps rather than saying "it's fast/slow/etc", and giving CPU metrics, give metrics related to something tangible - say, how long it takes for the penguin to drop - that is, not swinging at him. For me it's about 2-2.5 seconds. With the game running [not doing anything, just sitting there], it eats about 15% of my CPU. In terms of graphics cards, I have a Matrox G450, and run in xinerama mode.
While it appears to run fine on my system, I do notice that ESD [the sound driver] is taking up way more CPU than it needs to [50%]. However, this appears to occur more so after I have closed the Mozilla window....
BTW, someone claimed a distance of just shy of 200. My best is around 320.... ;)
