2003 Web Server is running slower than my XP version

[sheykc]

I'm in a crisis here. I just realeased a new web app last Monday. Apparently, something didn't show up in testing of about 7 or 8 people. When we went live, it jumped up to 15 to 25 users. The server is running so slow right now, people time out.

The main page that causes the problem is a page that can contain 1000+ items. We tested this before and the problem wasn't so noticeable.

This page has a datagrid and stepping thru the code, everything works as it should (on my XP web server). But as soon as I push out the code and 1 or 2 people start saving this page, my 17 second save turns into a 10 minute save up to 30 minutes and then times out. When you click on the save button, .NET seems to take forever after you click the button, before it breaks on the btnSave.Click command (like several seconds to a minute or 2)

The main difference is that I use Windows XP and the server is 2003. It's a dual processor with gigs of memory. I didn't set it up, but my own server just uses the defaults. I think that's how that server was setup too.

Can anyone help me with this?

Thank you, VERY much in advance.

Shey

 

[logicalunatic]

Shey,

1) make sure you've built the application without debugging.

2) For the datagrid, please see if you've used a DataSet or if you're just using a reader. A DataSet is overkill in my opinion if you're just displaying a list of rows for viewing or saving. Try a datareader instead or better yet...

Create SqlConnection
Create SqlCommand
Create SqlDataAdapter(SqlCommand)
Create DataTable
SqlDataAdapter.Fill(DataTable)

Bind DataGrid to DataTable

 

[ca8msm]

Also, you could try adding tracing to the page and then write out Trace.Warn statements at the start and end of each section of code - you should then be able to narrow down which line(s) are taking a long time to execute.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[sheykc]

I'll try both of these ideas, thanks.

We have uncovered another 'bizarre' behavior. When our users, use a VPN to connect to the web server, it runs seconds, sometimes minutes faster than if they access our internal web site, thru our internal server.

Have either of you seen that behavior before?

 

[jbenson001]

By you last post, it seems to me that there are some internal networking problems. Do you have other applications running that pull back a lot of data as the one you describe? You may need to talk to your network administrator.

Jim

 

[sheykc]

We're bringing in another consultant from my company who is a network specialist. It looks most definitely as though it's a network issue, not a programming issue.