Conference utrop1::linkworks_v3

2162.0. "Performance issues on logout..." by KERNEL::SIMPSONR (fred) Tue Mar 11 1997 15:26

LinkWorks V3.07 Ingres  Unix V3.2 (850 users)

I have a customer who says that his system practically grinds to a halt when
all the user's logout at the end of the day and they see real performance
problems. I found an article that might be of help. It was:

    During Logout the changes that the user made in the icon positions
    in any folder on his desk are stored in the schreibt table. In 2.1.7
    this was done at every move but in 3.0.x this is delayed until th eend
    of the session as you might move an icon several times. Further more
    the user status is updated to reflect that the user is logged out. The
    client may contact more than one cell. Every thing is done as regular
    RPC's no special ports etc are contacted. We corrected in 3.0.8 a very
    inefficient SQL statement that caused in particular Ingres to take
    several minutes when the number of rows in the table schreibt gets in
    the order of 100000 used to cleanup rows in schreibt that are no longer
    valid. (if the user deletes a folder, the rows of its (if any) children are
    renmoved from schreibt during logout).
    The processes involved on the server are TDF and CELLD.

The system is stable and so they do not have any intention of going to V3.08.
They will wait until V3.2 has been properly tested in house and upgrade then.
He says that the problem has worsened over time. Now when the user's logout at
the end of the day, the system goes wild. They have 80 to 100 celld processes
sometimes. TDF is working hard. He would like to ask two questions about the
information above:

 1/ Is there anyway to NOT save the user's icon positions on logout, so as to
    reduce the problem.

 2/ Where has the 'SQL' code been changed. Is there a way to get them the fix
    to apply to their V3.07 system?

Any help would be appreciated....
Cheers,
Richard Simpson

    You can use list mode to reduce the problem.
    
    You could decide to upgrade the server to 3.0.8 and leave the clients
    on 3.0.7. That's what I would recommend.
    
    Martin