The Amino Speed Project

I saw that you as a background on amino uses an image of 1x1 pixels, I do not understand why because it would be far better to just use a background color: #f0f0f0. You do not need to use an image for the background, it does’nt do any good.

On behalf of our developers, I would like to thank you!
They get a lot of inspiration and that is good.
They are working on it and we should see a result within the next couples of weeks.
If you have more ideas, please let us have them here :-)
Again thank you.

Cheers

Martin

Hi Guys

Here is a couple of performance tips from me.

First of all if you are not profiling you should be, the key element of all performance tuning is figuring out where the time goes.

Personally I use DotTrace from JetBrains for serverside profiling and Firebug for client based. You could have a look at DynaTrace they have the only tool I know off that provides end-to-end profiling (Cool Stuff)

Check out this blog http://madskristensen.net/ it provides a lot of good tips on how to tune ASP.Net focusing on a from the server part.

CQRS is all the rage these days, stands for Command Query Responsiblities Segregation, I would recommend looking it up on the net, understanding it and see if any of the ideas can be applied to Amino. I am currently doing a performance optimization, based on some of the ideas of it, and it's going to make writes in CloudSprout somewhere between 100 to a 1000 times faster.

If you a not on a 64-bit system, you really really need to be, it solves a lot of memory and related stability problems. Also the database needs to be on a 64-bit system, as it really likes the extra memory that can be allocated.

Did you know that .Net 4 is significantly faster and better at garbage collection then it's predessessors. Upgrading to it is highly recommended.

Also Microsoft has finally done a distributed cache engine, it's called AppFabric Caching and is availible as free download. It's very cool and definiately worth a look.

One of the coolest and most efficent ways of performance optimization is of loading work via Message Queue and updating the cache. When running a semi-big site such as Amino, I would definiately read up on MSMQ (It's free :-)) It is one of the secret to how sites like Ebay, Amazon etc. scales.

Gook luck with your work, I am looking forward to a faster Amino.

Rasmus Lindgren:

Jacob Rohde:

thevicarious:

Jacob Rohde:

Currently it takes about 2-5 seconds to generate the page depending on content, and that does seem ok I would say.

5 seconds for a site like Amino is not okay, Id say.

An avg. of 3 seconds, with a worst case of 5 is fine, I would say.

Not sure how this relates to a "forum" like Amino, but I would work on that response time if I were you:

http://www.pearanalytics.com/blog/2009/how-webpage-load-time-related-to-visitor-loss/

 

Unless I am misreading that chart - 3 seconds seem fine in relation to user loss.

Jacob Rohde:

Unless I am misreading that chart - 3 seconds seem fine in relation to user loss.

Why settle with "fine" ?

As others have pointed out in this thread there are loads of things that can be done to optimize the site. Some can even be done rather quick and at minium costs.

I don't understand why you would ever settle with second best and the article at pearanalytics clearly states that every 100ms added to loadtimes have a negative effect.

Martin:

Why settle with "fine" ?

Lundsby:

CQRS is all the rage these days, stands for Command Query Responsiblities Segregation, I would recommend looking it up on the net, understanding it and see if any of the ideas can be applied to Amino. I am currently doing a performance optimization, based on some of the ideas of it, and it's going to make writes in CloudSprout somewhere between 100 to a 1000 times faster.

Thanks for that - I will look into it, and see how it relates to our stack.

Lundsby:

If you a not on a 64-bit system, you really really need to be, it solves a lot of memory and related stability problems. Also the database needs to be on a 64-bit system, as it really likes the extra memory that can be allocated.

Yeah, we are all 64-bit

Lundsby:

Did you know that .Net 4 is significantly faster and better at garbage collection then it's predessessors. Upgrading to it is highly recommended.

Yeah .NET 4 is awesome. Most of our new services run in .NET 4. Our CS stack run in 3.5 if I am not mistaken.

Lundsby:

Personally I use DotTrace from JetBrains for serverside profiling and Firebug for client based. You could have a look at DynaTrace they have the only tool I know off that provides end-to-end profiling (Cool Stuff)

JetBrains make some awesome products! I couldn't code without R#. Anyways, we actually just purchased dotTrace the other day beccause of a perf problem we had. It is expensive but worth it. It took me perhaps ten minutes to find the culprit.

Thanks for your input - appreciated.