Someone jump in if I'm all wet, But I think your results are low.
(1) Yes Running the benchmark on an SSD that is say 1/2 full will normally be lower than right after a fresh install.
(2) The Force 3 Uses a SF22xx controller. The AS SSD program uses data that is NOT compressable, The SF22xx great benchmarks are normally with data that is easily compressable. Real life probably inbetween, maybe a little closer to the Non compressable side at least for a boot/program drive.
(3) Earlier today I had to look up the performance for my Curcial M4, uses the marvel controller.
128 gig M4 Intel Chipset, Rst ver 10.6
Have two and both score almost Identical.
Seq..... 501.97 ...... 194.29
4K ...... 22.28 ....... 49.21
4k-64 . 296.64 ...... 155.71
Acess .. 0.089 ....... 0.202
Score....... 369 / 224
Overall ......... 774
http://www.tomshardware.com/forum/forum2.php?config=tomshardwareus.inc&cat=32&post=273654&page=1&p=1&sondage=0&owntopic=1&trash=0&trash_post=0&print=0&numreponse=0"e_only=0&new=0&nojs=0
Two things, (A) I'm just not sure where the F3 stands compared to the vertex 3 and the M4. But I'd say your scores are considerably lower than they should be. (B) All my experience (have 8 SSDs) are on Intel chipset systems. About 6 months to a year ago SSDs (Sata II versions) performed better on Intel chipsets. AMD users werre complaing that amd was dragging their feet developing a driver and users were stuck using uSoft default AHCI - I think they corrected their problem, but unsure.
Hopefully a AMD user can jump in and offer some better advice and if amdata is the correct driver.
Apologize for my limited brain functionality.