Could ATRL's source code be suffering from occasional endless loops? Or redundant repetitions?
Could it explain why the server's been inconsistent?
I think Ulrihs perfectly summed up some of the best assumptions as to why is this happening:
Quote:
Originally posted by Ulrihs
ATRL is quite messy form code point it seems. Even if you look @ source for page that is returned there is lot of garbage that is sent to client every time. Not to mention that there is lot of styles that is placed directly in page and not in separate file that is linked with:
Code:
<link rel="stylesheet" type="text/css" href="url" />
But that makes it longer for client to load page, not for server to be slow.
There can be lot of reasons why site become slow with time:
1) Objects are not disposed when they are no more necessary
2) Cached data was not cleared and stay in memory even none need it anymore
3) Open connections with database remains open
All those leads to memory leak and at one point server has no memory left and all stops completely.
If site is slow all time usually that means that problems is with code behind. Often error that i was seeing was displaying lists with some columns that are with calculated data. Instead of making one more complex query that fill all columns on database side, there was one basic query that returns list with some columns and then for every row there is additional call/s to database to fill left column data.
I can't tell what wrong is with ATRL there can be lot of problems, including DoS attack or virus, but site clearly needs some polishing. |
