ranXerox's dashboard

RAM is not an issue since its a pure cosmetical problem. CPU seems to be high when maintaining files sometimes, so I guess Wuala recalculates fragments or something... – Bugreport, on October 10, 2008 08:34

It's really bad. When I restart wuala it's better in the first time but the RAM usage is running up to 290 MB and then also the usage of the CPU

I keep getting this program randomly, when uploading/downloading/maintaining. Restarting wuala, seems to fix the problem -- but its really annoying.

Oi! Here as well! Maintaining files seems to use quite some CPU cycles (wasn't always like that...). I just logged in on my storage node and clearly see the reported behaviour. Wuala also reports (inside Wuala - about box!) 116 MB(!) RAM used.

Something seems really wrong here...

Client: 108
Windows 2008 64bit, FSI activated + works flawlessly

After some time however the usage went down. Maybe Wuala did calculate new fragments?!

EDIT: While it doesn't seem to max out during upload anymore. It is now maxing out, when it is "Maintaining" a file. – bdb4269, on September 17, 2008 18:04

EDIT: I just checked again -- and this problem seems to be fixed (or perhaps it doesn't happen all the time) --- I'll assume it's fixed, and I will post back, if I experience the problem again. – bdb4269, on September 17, 2008 17:52

Agreed -- it's the maxing out the CPU thats killing me!!!

I'm running XP with 1.5GB RAM, so I could care less about the mem usage.

I have also found that this (the CPU 100%) only seems to happen, when it is currently uploading data. When it is just running doing it's thing with the space I am trading, it does not run the CPU up. Only when I add stuff to my files. (and it doesn't just max out, when it's doing that initial "add files..." part, that has the progress bar -- even after that is done, and it's just uploading the data, (little green bars by the files in wuala) it still max's out the CPU)

Another small detail I noticed -- that may or may not be significant. I started wuala, uploading when I was done with my PC one night. I normally stay logged into the PC, but I remote desktop'ed to it real quick that night -- so it was at the welcome screen in the morning. I logged in, and noticed first thing that wuala was maxing my CPU -- So I immediately un-minimized task manager --- and looked at my CPU graph -- I could see all the way back, it was running at >10% -- and it just spiked to a 100% plateau when I logged in. I haven't tested this to see if I could recreate it -- but it seemed weird, that it would max it out only after I logged back in.

This only happens on 1 of my PC's. On my others, when it is doing the initial "add files...." part -- it doesn't max out the CPU, but it does tax it to about 30% --- and once the "add files..." part is over, and it is just uploading data to to the network, (green bars by files), the CPU goes back down to <10> part is over, and its just uploading.

If you want me to troubleshoot/try anything, or provide logs, an everest report, a hijackthis report, or anything else that might help, just let me know.

anyhow, the thread you suggest is just about memory...while I do not really care about memory as my machines have enough, its the high CPU load that is really bad.

...or it's time for people to actually LOOK at the threads getsatisfaction suggests! D'oh!

siehe
http://getsatisfaction.com/wuala/topi...
--
schön langsam wird es Zeit für ein besseres Forum