I noticed that Tangler feels a bit slow.  What kind of scaleability does it have?  How long has it been publicly known and what kind of user growth are you prepared for?  Now that invites are out into the tech crowd, will the Digg/Fark/Slashdot effect kill the site?

Typing posts into the browser, it pauses after about two lines of text.  The keyboard buffer so far has been able to keep up with my typing, but it's disconcerting when you're typing along and the screen stops putting up the letters.  For those of us who no longer have to stare at the keyboard keys when we type, the screen is our primary feedback device for whether or not it's working.

Definitely, the response to the typing is slow. And certain things such as the add link menu and such are pretty slow. I also agree with the rest of the stuff your saying.

Big area for us rg... we made some pretty major changes in this release to speed things up. Unfortunately we also managed to slow other things down.

We're beavering away. Responsiveness is a big priority.

I've just joined and it is still painfully slow to use. It takes five to ten seconds for the recent activity dropdown to propagate and sometimes it just drags the rest of my browser down with it, so I can't change tabs or anything. It's not my connection because everything else is fine. Are there any known issues with particular software combinations? I'm (temporarily thank goodness) on Window Vista/Firefox but have Azureus running in the background too.

 

We could use your vote to put pressure on the devs to develop either a lo-fi version or an API, or both.

I usually don't notice much slowdown actually - I am looking for hopefully more activity from varied participants.

It seems a bit better this evening so i shall bear with it for the time being!

@Nico, there is one particular combination that is pretty lethal to tangler (and most other javascript applications): the firebug plugin for firefox. if you have that installed try disabling it when using tangler, it makes a big difference.

Firebug? Don't think so. What does that plugin do?

What sort of computer are you using?

At the moment Tangler does execute a lot of javascript, which can make it heavy on the client on slower machines. We're working on reducing the overhead in the next few releases.

Marty: I look forward to that with great anticipation!

[In my personal experience, ]Using Tangler feels like running a Win 3.1 application on a 286.  :\

@Marty I'm using a laptop with 2Gb of RAM and dual-core Pentium inside.

Nico: that should be fine. Could I ask what you're latency to tangler.com is? Right now we load a lot of objects, so latency can be an issue if you're relatively far away. Another thing we're working on.

You can find out latency by "pinging" tangler.com - on windows select run.. from the start menu, type cmd and press enter. Then type ping tangler.com and report back the number it shows.

Mine is:

C:\Users\marty>ping tangler.com

Pinging tangler.com [208.75.56.106] with 32 bytes of data:

Reply from 208.75.56.106: bytes=32 time=41ms TTL=50
Reply from 208.75.56.106: bytes=32 time=40ms TTL=50
Reply from 208.75.56.106: bytes=32 time=43ms TTL=50
Reply from 208.75.56.106: bytes=32 time=42ms TTL=50

Ping statistics for 208.75.56.106:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum = 43ms, Average = 41ms

So, 41ms average.
 

I get 203ms, is that good or bad?

It's normally quite fine. But because right now Tangler has you loading lots of different objects (bits of code, images, html) it causes a higher degree of delay than it normally would. Right now lower latency connections will make Tangler appear faster. Reducing the number of objects being loaded is something we're working on as well.

Hey Marty,

Just passing through,saw this group and tried the ping - I get 377ms average - but that's on my dial-up. I have noticed my gmail accounts being even slower than usual lately and tangler too . Mind you my system is probably due for a clean as it has slowed down considerably itself the last month or two. Sorry about the dual message, I keep forgetting what happens when I hit "Enter" to start a new line/para

whoops , like that

377ms is going to make things pretty slow unfortunately. At least at the moment.

I'm getting around 200ms this morning so that is good!

I just tested now, and get 78ms consistently.  If mine is "that fast", it says something about the amount of JS and stuff you guys are using...

Pinging tangler.com [208.75.56.106] with 32 bytes of data:

Reply from 208.75.56.106: bytes=32 time=168ms TTL=53
Reply from 208.75.56.106: bytes=32 time=199ms TTL=53
Reply from 208.75.56.106: bytes=32 time=206ms TTL=53
Reply from 208.75.56.106: bytes=32 time=163ms TTL=53

Ping statistics for 208.75.56.106:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 163ms, Maximum = 206ms, Average = 184ms

And it's slow here as well. I'm sitting on a 1gbit connection, 2gb ram, dual-core system, so it should be BLAZING along

A vote for the API!

/me wants tangler in his Pidgin...
 

Amethi: could you tell me which browser you're using?

I'm using the latest version of Firefox and it is slower than I would like.