|
Home > Archive > Certified Internet Webmaster - CIW > June 2001 > Is ASP slow?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| BootData 2001-06-08, 1:51 am |
| hi. there...
Finally my boss asks me to do some web development...I'm putting together a solution for a webstore (i'm suggesting to build using ASP + combined with Commerce Server 2000).
but my technical team says that ASP is very slow in performance..is this so? any alternative? FYI, the current load is only about 1000hits per day
any feedback is greatly appreciated..
thanks | |
| appomattox 2001-06-08, 11:21 am |
| ASP is not slow. CGI scripting is slow. With 1000 hits a day you wouldn't notice the difference regardless. If you had 1000 hits a minute CGI would seem slow, pretty sure ASP would still be able to handle it in that situation. | |
| cboyles 2001-06-09, 12:53 am |
| I gotta go withh Appomattox on this one. I have done a load of CGI Dev and ASP dev in my time, and I have to go with ASP. Speed is contingent on many variables, such as with regular front end dev. ASP's process very quickly. I have noticed that alot of lag can come from an MS Access connection, but most of the lag can be attributed to poor programming. Go with ASP. You'll be happy especially if your in an MS Shop. Commerce Server isn't a bad product either, just a caution before you build remember if you ever need to port this web to a new machine, the new box should be a Commerce Server too. I have had to clean up a lot of reported commerce webs, it's not pretty! | |
| BootData 2001-06-10, 5:04 am |
| cboyles, appomatox...thanks for the input.
your postings justify my initial consideration for choosing ASP (over CGI, for example).
since the client's infrastructure is using Microsoft product, this is making sense 
cheers,... | |
|
| also............
weigh up whether u want to use dsn or dsn-less conns as there are varied opinions on the speed of both......
also (i think) Access can only handle 256 concurrent connections, which you may want to take into account if its receiving 1000h/pd.....
an alternative to ASP would be PHP which is meant to be a tough language, but i'd go with asp
btw, im in aust. too | |
| cboyles 2001-06-10, 10:04 pm |
| Yeah I didn't even think of that.
Cheers | |
| SasiSan 2001-06-12, 8:11 pm |
| I would definately go with ASP. The problem with the slow-fast also comes to development time. If you know VB and Microsoft you can produce better, faster with ASP. If the other guys know Unix then they are going to cheer on the product they are more comfortable supporting.
If you code it right -- ASP shouldn't be slower. Upgrade Access DB to SQL Server eventually. You should be able to get around the connections because the ASP can use one account to access everything -- especially if is a reporting type project...
 | |
| BootData 2001-06-14, 9:14 am |
| dear all,
thanks for the replies,
my team and I have confirmed...Commerce Server 2000 + some ASP will be used!
cheers, |
|
|
|
|