Hi,
I'm just working on a page here that's ment to display a link if a certain directory already exists on the server. DirectoryExists() does the job fine.
Does anyone know what kind of implications/impact there'll be if the page is called many many times (ie: intranet homepage kind of traffic levels)?
Mostly worried about it making the server cry.
Thanks!
-Joel
********************************* DISCLAIMER *********************************
The information contained in the above e-mail message or messages (which includes any attachments) is confidential and may be legally privileged. It is intended only for the use of the person or entity to which it is addressed. If you are not the addressee any form of disclosure, copying, modification, distribution or any action taken or omitted in reliance on the information is unauthorised. Opinions contained in the message(s) do not necessarily reflect the opinions of the Queensland Government and its authorities. If you received this communication in error, please notify the sender immediately and delete it from your computer system network.
how does your app perform with your max expected number of users
and directories being checked?
file systems are pretty fast these days.
jmeter is pretty easy to setup to test this kinda load, there's a
quick guide on my blog if your intersted
--
Zac Spitzer -
http://zacster.blogspot.com (My Blog)
+61 405 847 168
I think it wouldn’t be too bad, but there might be smarter ways.
What about recursively browse the directory once and build a struct, then you can use if structKey exists
Regards
Dale Fraser
you can always refactor for performance later and if you built it with
maintainability in mind, refactoring should be pretty straightforward
and painless
One of things we as developers tend to ignore, well maybe not ignore. But we
do try to emphasise to much on getting it right the first time, the pressure
from clients to do this is let's say a big factor in the equation.
However it may never become a problem, and may scale very well. But as Barry
has indicated, one can always revisit and refactor if it ever does becomes a
problem.
Regards
Andrew Scott