How much score in GRE computer science subject test is considered 'good'? I'm applying to MS / MS-PhD programs in CS this fall. 

I don't have a good GPA (2.86 on a scale of 4). I have experience as a research assistant under a professor and also a couple of good projects. 

Right now I'm working as a developer, so I have around 5 months of experience. I have a GRE score of 314 on 340. I'm giving subject test to improve my chances of getting into a grad school. What score can be considered 'good'? I don't have much time to prepare and I am a little rusty on some of the topics, what is the good advice for a crash course for subject test in, say a week or so?
As @davidshen's answer points out, my answer is now moot, because the GRE subject test in computer science is no longer offered.



For most applications to strong departments, there is no good score on the GRE CS subject test; there are only bad scores.  A score below the 50th percentile is a red flag, indicating significant gaps in your undergraduate CS background.  (The raw score is completely meaningless to most people, even those of us who work on admissions committees; only the percentile score matters.)  But graduate school is about research, not standardized tests, so no GRE score is good enough to get you accepted.

There are a few exceptional circumstances where a high GRE score actually gives some useful information.


As Daniel says, a score in the 90th percentile or better can partially make up for a poor GPA.  (It worked for me; my GPA was worse than yours.)  It's probably not enough on its own, though.  (It wasn't for me.)
GRE scores are useful for calibrating GPAs of students from unknown schools.


On the gripping hand, many graduate programs (like mine) don't require GREs; their admissions committee may not even think to look at your GRE score unless you point it out in your statement of purpose.