Hi, I'm on FF 3.5.3 on Ubuntu 9.04 64bit here. Altough I use a umts connection the waves load fast. Does not matter if there are 30 blips or 250 and also + 5 gadgets in there.
How are you connected to the internet? Maybe this is the bottle neck? Or maybe your pc is running on 100% because of the huge javascript processing? If nothing mentioned above is the case this is maybe a gentoo specific issue. I will start my dusty gentoo box and try if I can reproduce your experience. Btw, bug reporting here: http://code.google.com/p/google-wave-resources/issues/list (but as I already said, it seems not to be a wave issue in your case) On Oct 5, 10:35 pm, Mike <[email protected]> wrote: > I'm sure this has already been mentioned somewhere, but just wanted to > do my part and report my experiences. > > I'm accessing the developer's sandbox with Firefox 3.5.3 on Gentoo > Linux and it is SLOW. > > A wave with very few wavelets (<5) loads ok, but anything with much > more than that has significant lag. Waves with 60 wavelets take a good > 20 seconds to load and big conversations with 300+ can take almost 2 > minutes. There may be no way around this, but if so even some kind of > progress meter would be an improvement. Right now there's a lag > between the time I click the wave in my inbox and the time anything > displays, with no feedback so I'm not sure if my click was registered. > Then the wave starts to display but there are still parts of it > loading, with no easy way to tell when it's done. I try to wait > because attempting to scroll or interact with the wave in any other > way doesn't work very well until it's fully loaded. > > The custom scrollbar doesn't work very well for me either. It's ok if > I just use the arrows to page up and down, but if I try to scroll by > dragging it it's all over the place. I think it's because the "shadow" > of the scroll component that actually controls the scroll offset lags > behind the draggable component instead of sticking with it 1:1. So if > I'm visually scanning the wave for something as I scroll, by the time > it's displayed I've actually already scrolled past it and have to go > back. I end up wobbling back and forth around the area I'm trying to > hit for several seconds. Again, this is much much more noticeable on > bigger waves, because each dragged pixel represents a bigger scroll. > It's still an issue on small waves, just not as bad. I'd rather deal > with an ugly native scrollbar widget at this point. > > Also, there is an extreme lag when I type into a wave. As with > everything else, it seems to be proportional to the size of the wave / > number of participants. In a big wave I can type a 7 letter word and > then have to wait a second or two for the display to catch up at the > end. If I write a whole sentence it often takes 30 seconds or more. I > assume it's due to the transmission of each character as it's typed so > others can see it show up on the fly. Hopefully when Draft mode is > enabled it will cut out that transmission completely and work around > the problem. If so I hope there's an account setting where I'll be > able to choose Draft mode by default - it would be very tedious to > check it every time I wanted to type something. > > Aside from the slowness there are a few HTML glitches but they're much > less problematic. Notifications at the top of the wave, like "[not-yet- > implemented-user] gave everyone access]" tend to overlap the top of > the wave content. If I start a reply with a bulleted list, the first > bullet line is shifted too far to the left and overlaps my name. The > second line overlaps my image a bit (and the bullet is bigger and > green for some reason). The first correct line is the one lower than > my image - I assume it depends on my font size. Maybe it just needs > some kind of forced float clearing for the "me" block before it starts > the bullets? > > Don't take any of this as complaining, just bug reporting. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
