Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Database application is running too slow. User Suffers alot


  • Please log in to reply
1 reply to this topic

#1 Faheem316

Faheem316

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:12:36 PM

Posted 03 January 2018 - 03:30 AM

I am using windows server 2003. Oracle 10g. Toad oracle version 9.0.1 MS visual studio 2010. When users access the application through browser the application loading causes too much time or Following error occurs.

 Sys.webFroms.PageRequestManage Timout Exception. The server request timed out. The application runs too slow or pops up the above mention error.

Kindly mention the reasons why its too slow how to solve this issue.


Edited by Faheem316, 03 January 2018 - 03:32 AM.


BC AdBot (Login to Remove)

 


#2 RecursiveNerd

RecursiveNerd

  • Malware Study Hall Junior
  • 239 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Louisville, KY
  • Local time:03:36 AM

Posted 03 January 2018 - 09:14 AM

What you're asking for is nearly impossible to respond to without knowing how you're accessing your data, the database schema, as well as how the application requests and responds to data.

 

The accessing of data should be done asynchronously such that the application doesn't hang up while the request takes place. Since I can't give an exact answer without knowing the full technology stack, I can only suggest you search the specific error(s) on your favorite search engine. Typically, if the server spins up a long running process, such as accessing lots of data through a stored procedure, it is best to look at the server side and try to understand why it takes a long time and what you can do to reduce the time it takes to run.

 

There are several applications out there that can help you debug what is going on through the client application. Fiddler is one such application where you can see which requests are made and how they are being satisfied by the server.

 

Here's Microsoft's documentation on the error, FWIW.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users