stats server upgrade
Posted: Fri Jan 30, 2009 3:12 pm
"In 2009, we will be upgrading our stats server such that the whole database will fit in RAM (this used to be the case, but FAH has gotten quite big over the last few years and the related databases require over 20GB). We expect that this new stats server should greatly speed up stats updates."
Source: http://fah-web.stanford.edu/cgi-bin/mai ... =userstats
Why not cache the DB using 64 GB CF SSD? (Instead of RAM).
I don't know how long it took for the DB to get to the size that it currently is, and I don't know how long F@H has been running for, but I would think that if the trend continues the way it is, that you'd probably be able to fill 64 GB in a few years. So unless, there's going to be plans to upgrade again at that time, otherwise, why not go with something like a 64 GB CF SSD.
I suppose you could always build the system out to be nearly a DB cache server (128 GB of RAM) and then stagger the DB updates and/or incremental updates using grouped transactional disk I/O.
*ponders*....
Source: http://fah-web.stanford.edu/cgi-bin/mai ... =userstats
Why not cache the DB using 64 GB CF SSD? (Instead of RAM).
I don't know how long it took for the DB to get to the size that it currently is, and I don't know how long F@H has been running for, but I would think that if the trend continues the way it is, that you'd probably be able to fill 64 GB in a few years. So unless, there's going to be plans to upgrade again at that time, otherwise, why not go with something like a 64 GB CF SSD.
I suppose you could always build the system out to be nearly a DB cache server (128 GB of RAM) and then stagger the DB updates and/or incremental updates using grouped transactional disk I/O.
*ponders*....