Skip to main content
S
steak1986
Participant
August 15, 2011
Question

Access Dbs, win2k8 r2 x64, and cf9

  • August 15, 2011
  • 1 reply
  • 968 views

I didnt know under which subject this should go, so its here and coldfusion,

I have a server that is a win 2008R2 x64 SP1 IIS7.5, with CF  9,0,1,274733.  Just migrated from win2k3 with IIS6 and CF 7mx.  Now that we have migrated, we tested the pages and all seemed well.  Now that people are running queries its is running slowly.  Getting a bunch of timeouts.  Something is obviouslly not right.

The only thing i can think of that is causing our weirdness, is the fact that we were using Access Dbs, which from what i have read are a big legacy no-no.  I have followed this document which was pointed in another thread in the forums,http://www.cfexecute.com/post/access-dsns-in-64bit-coldfusion/ .  I have followed the directions, our pages work when i test them.  However when our staff of at least a 100 people come in and start banging against our server, bad things happen.  The server has a bunch of timeouts, request times are very high.  The site is just very slow.  Anyone have an idea?  I can provide more info, i just feel stumped

This topic has been closed for replies.

1 reply

A
Adam Cameron.
Inspiring
August 19, 2011

Access is not a multi-user DB, so it's not really designed to cope with 100 people using it at once.  Sure, strictly-speaking only the CF server is connecting to it (one user), but it's doing it on behalf of 100 other users, so it amounts to the same thing.

If you can't just migrate away from Access (which is what you should do), you might be able to finetune stuff that is performing particularly badly.  Get hold of FusionReactor or something and have a look at what JDBC activity you have, and which DB requests are causing issues.

If you can't or won't pony-up for FusionReactor, even turning debugging on and load-testing in a dev environment might show some stuff up.  Running with debugging on automatically adds overhead to all requests, but you should still be able to spot spikes in performance due to slow DB activity.

--
Adam

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices