What about the performance between the states that can be stored on the server

[Tony Johansson]

Hello!

On the server you can store threse states Session, Application and Cache.
I know what they mean so you don't have to explain that but what I don't
know is if there is any difference in performance
when comparing them.
I assume that the cache is stored in a special memory that is faster then
the memory that Session and Application is using.
is that correct ?

//Tony

 

[andy]

Hello!

On the server you can store threse states Session, Application and Cache.
I know what they mean so you don't have to explain that but what I don't
know is if there is any difference in performance
when comparing them.
I assume that the cache is stored in a special memory that is faster then
the memory that Session and Application is using.
is that correct ?

//Tony

No.
They're all stored in memory on the web server or on a different
server or in a sql database.

 

[Arne Vajhøj]

On the server you can store threse states Session, Application and Cache.
I know what they mean so you don't have to explain that but what I don't
know is if there is any difference in performance
when comparing them.
I assume that the cache is stored in a special memory that is faster then
the memory that Session and Application is using.
is that correct ?

No. By default they are all stored in ordinary memory.

And therefore they are very fast.

The tricky part comes when you go from single server to
cluster environment and you want/need to keep this
stuff available for all servers.

You may not need to. If cache is just used for cache of
database data, then you may be OK with having a separate
independent cache on each server. If you can live with
users having to startover in case a server goes down,
then using a load balancer with sticky session may
solve the problem for sessions.

If you want the same stuff available for all servers
in the cluster then it costs.

Storing in a database instead of memory is a factor
1000 (or something like that) slower.

Replicating directly between servers (often using UDP
multicast and similar) is pretty fast, but also a bit
complex and does not scale linearly.

Arne