Very Slow Speed w/ Opening Adobe Documents

Question

We just installed Adobe X Pro to a corp computer.  We have faxes that come in and then renamed/ etc... as pdf files.  We are not new to Adobe document use.  Since this installation, my Adobe files are opening VERY slowly- takes 15-25 seconds for each document to open, then when I close them to move to a folder, this process seemingly takes at least 15-30 secs per file. I did not have this issue previously.  Other internet based files are opening without delay, so I know that it must have something to do with the Adobe settings.  HELP!!

Answer 1

I put the output from dmesg here:
http://pastie.org/private/cprjtnsu24q72fkkjuisjq
I noticed some errors like this:
[ 1474.695990] ata1.00: status: { DRDY }
[ 1474.695993] ata1.00: failed command: WRITE FPDMA QUEUED
[ 1474.695999] ata1.00: cmd 61/00:30:08:0e:39/04:00:06:00:00/40 tag 6 ncq 524288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
I had already fixed this problem by adding libata.force=noncq to my kernel parameters, I guess I forgot it when I added allow-discards
So here is the dmesg after with libata.force=noncq added:
http://pastie.org/private/c5gkanfihqsunbf6sdgyva
I noticed something else. I created several 1G files using dd. The speed slowed down with each file:
dd if=/dev/zero of=./swapfile2 bs=1024 count=1048576
1048576+0 records in
1048576+0 records out
1073741824 bytes (1.1 GB) copied, 65.5381 s, 16.4 MB/s
dd if=/dev/zero of=./swapfile2 bs=1024 count=1048576 0.27s user 5.58s system 8% cpu 1:05.54 total
dd if=/dev/zero of=./swapfile3 bs=1024 count=1048576
1048576+0 records in
1048576+0 records out
1073741824 bytes (1.1 GB) copied, 144.525 s, 7.4 MB/s
dd if=/dev/zero of=./swapfile3 bs=1024 count=1048576 0.25s user 6.08s system 4% cpu 2:24.53 total
dd if=/dev/zero of=./swapfile4 bs=1024 count=1048576
1048576+0 records in
1048576+0 records out
1073741824 bytes (1.1 GB) copied, 356.969 s, 3.0 MB/s
dd if=/dev/zero of=./swapfile4 bs=1024 count=1048576 0.23s user 5.23s system 1% cpu 5:56.97 total
My guess is that the first file was written to space which was formely occupied by another big file. When I deleted the former file trim worked it's magic hopefully. This made me remember, when I followed the Installation guide there was a step I did which overwrote my drive with random data.
What I'll try now is creating a file that  takes up all remaing space like above and then deleting it. Do you believe this might work?