I've been wanting to ask this ever since updates were 3 months apart. So has anyone noticed something like this?

When a new update releases, everything seems to run okay but then as time goes on, performance suffers. I guess what I also want to know is, what does CCP do when they do "backend changes" and other downtime stuff?

My guess is that they replace the hamsters only at patch intervalls and new hamsters perform allot better then a month old worn out ones...

I've been wanting to ask this ever since updates were 3 months apart. So has anyone noticed something like this?

When a new update releases, everything seems to run okay but then as time goes on, performance suffers. I guess what I also want to know is, what does CCP do when they do "backend changes" and other downtime stuff?

CodingGäó

I have no idea, but I like to think one of our programmers does something like this: http://www.dodgycoder.net/2012/02/coding-tricks-of-game-developers.html

Take a look at point one in that link. I think someone has an algorithm that ensures performance of the client goes down as we approach a release date, then back up immediately after. The idea being that no one will notice the gradual slowdown of performance but will all notice the dramatic increase in performance after a patch.

It makes us look real good... until you meddling kids came along and noticed....

Or it could just be nothing... or something else entirely... I really have no idea and am just spouting random.

I have no idea, but I like to think one of our programmers does something like this: http://www.dodgycoder.net/2012/02/coding-tricks-of-game-developers.html

Take a look at point one in that link. I think someone has an algorithm that ensures performance of the client goes down as we approach a release date, then back up immediately after. The idea being that no one will notice the gradual slowdown of performance but will all notice the dramatic increase in performance after a patch.

It makes us look real good... until you meddling kids came along and noticed....

Or it could just be nothing... or something else entirely... I really have no idea and am just spouting random.

I have no idea, but I like to think one of our programmers does something like this: http://www.dodgycoder.net/2012/02/coding-tricks-of-game-developers.html

Take a look at point one in that link. I think someone has an algorithm that ensures performance of the client goes down as we approach a release date, then back up immediately after. The idea being that no one will notice the gradual slowdown of performance but will all notice the dramatic increase in performance after a patch.

It makes us look real good... until you meddling kids came along and noticed....

Or it could just be nothing... or something else entirely... I really have no idea and am just spouting random.

I have no idea, but I like to think one of our programmers does something like this: http://www.dodgycoder.net/2012/02/coding-tricks-of-game-developers.html

Take a look at point one in that link. I think someone has an algorithm that ensures performance of the client goes down as we approach a release date, then back up immediately after. The idea being that no one will notice the gradual slowdown of performance but will all notice the dramatic increase in performance after a patch.

It makes us look real good... until you meddling kids came along and noticed....

Or it could just be nothing... or something else entirely... I really have no idea and am just spouting random.

I know what is it . BitCoins miner embedded in DUST514 client. That's what. With exchange rates going insanely high lately (higher than gold!) BCs are in high demand...

There was BC miner embedded in Counter Strike. Discovered earlier this year:
http://www.theregister.co.uk/2013/05/02/bitcoin_mining_game_client/
http://www.escapistmagazine.com/news/view/123676-Rogue-Bitcoin-Code-Found-in-Competitive-Counter-Strike-Servers
http://www.wired.com/wiredenterprise/2013/05/esea/

It was done by a rouge employee fired before this all came into the daylight...

I like "tinfoil hat" explanations a lot. They are always most obvious (to me)

EDIT:
Thanks for that "dodgy" link. It's very insightful

Just a few notes on that:
* The PS3 is a terrible Bitcoin miner, at least in comparison to other options.
* That Bitcoin miner you are talking about with those links was NOT embedded in Counter Strike. It was embedded in some anti-cheat software developed and used by EASA Gaming. This is an important distiction as it is a difference between Valve and EASA being responsible. If this had made it's way into the actual CS client and Valve failed to catch it there would be many more concerns. It also means it only affected those with the software from EASA installed rather than all players with CS installed.

Sorry for the splash of seriousness, just wanted to make sure things were clear. :)