We're constructing a system nominated SIGERE for planning, budget and financial execution. The objective is to use the SIGERE for all proccess in our company.
The company is CDTN - Center of Development of the Nuclear Technology, a Brazil company of the government which work in research and development of nuclear technology.
The system has about 70 business classes. It uses the persistent layer AtomsFramework and an interface layer in ASP.NET.
The system is about 60% finished.
The AtomsFramework is working very well except in some retrieve criterias which it's work a bit slow.
Thanks very much for that iniciative.
ps: excuse me because my bad English.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the feedback :-) And thanks for the code you submitted - it should be in CVS and the next version soon.
If you can give me some more specific details on the queries that are performing slowly I'll see what I can do to help. Maybe some information on the number of objects being retrieved, the round trips being performed, the efficiency of the query in the SQL server itself, etc
I'd like to make the framework as fast as possible under all circumstances, but as I saw in the last change I made to query generation I generally made things worse :-(. Obviously some sort of intelligent optimsations to the way queries are generated is required but I'll need to have a bit more information at hand before I get too serious about redesigning the core of the framework...
- Richard.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Um example which perform slow is a retriving of 807 registers of a table. Each register have 110 bytes of fields char and varchar.
Ai retrieve these registers and mount a combo box in a aspx page.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I assume you are using a retrieveCriteria or a getAll to get these objects.
A retrieve criteria (if done right) should only need one round trip to get all of the 807 records. You will only have a speed issue if you are getting associated objects for each of the 807 records since each association is processed record at a time.
What is the actual call you are using to get the data?
(you might also want to check that you are getting full objects insteaad of proxy objects)
- Richard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We're constructing a system nominated SIGERE for planning, budget and financial execution. The objective is to use the SIGERE for all proccess in our company.
The company is CDTN - Center of Development of the Nuclear Technology, a Brazil company of the government which work in research and development of nuclear technology.
The system has about 70 business classes. It uses the persistent layer AtomsFramework and an interface layer in ASP.NET.
The system is about 60% finished.
The AtomsFramework is working very well except in some retrieve criterias which it's work a bit slow.
Thanks very much for that iniciative.
ps: excuse me because my bad English.
Hi Marcos.
Thanks for the feedback :-) And thanks for the code you submitted - it should be in CVS and the next version soon.
If you can give me some more specific details on the queries that are performing slowly I'll see what I can do to help. Maybe some information on the number of objects being retrieved, the round trips being performed, the efficiency of the query in the SQL server itself, etc
I'd like to make the framework as fast as possible under all circumstances, but as I saw in the last change I made to query generation I generally made things worse :-(. Obviously some sort of intelligent optimsations to the way queries are generated is required but I'll need to have a bit more information at hand before I get too serious about redesigning the core of the framework...
- Richard.
Dear Richard,
Um example which perform slow is a retriving of 807 registers of a table. Each register have 110 bytes of fields char and varchar.
Ai retrieve these registers and mount a combo box in a aspx page.
I assume you are using a retrieveCriteria or a getAll to get these objects.
A retrieve criteria (if done right) should only need one round trip to get all of the 807 records. You will only have a speed issue if you are getting associated objects for each of the 807 records since each association is processed record at a time.
What is the actual call you are using to get the data?
(you might also want to check that you are getting full objects insteaad of proxy objects)
- Richard