Not particularly unfortunately. The locking required for one user's stats to be locally more accurate would be expensive code wise, and will adversely affect scalability of the overall pool. It's more important that the pool scales linearly with number of users. Currently the pool is servicing 12500 clients at 3200 transactions per second and could service about 20x that on the current server thanks to that scalability. At this stage there is no need to look at a bigger server as well as I'm not sure how long this hashrate will even stay with us, and unfortunately still expect a downturn again.