My apologies if this has been discussed.

We're universe 10.0.8.

 

When we run repeated SELECTs on files that presently are triggered, or have
been triggered (we did a drop trigger), we are seeing an increase in the
resident and paged memory for that user, and an eventual slowdown due
presumably due to program size or some other not easily seen inefficiency.
Jobs that used to finish in a couple of hours, now fail to finish in a 24
hour timespan. Please note that as in a previous controversy, no slowdown in
the updating of said triggered files is seen, other than normal trigger
write time. We have only seen the problem with multiple SELECTs done on the
triggered file, OR on the file after a drop trigger is done.

 

The problem happens whether or not the SELECT returns anything, whether or
not I drop the trigger and remove the voc item that is a path "F" type
entry. 

 

The problem is tested and observed using only a voc item that 

SELECTs q.pointer.file.name with an.indexed.field = "a value", 

followed immediately by a 

CLEARSELECT.

 

The problem doesn't happen for non-triggered files of both distributed and
'non-distributed' ilk. 

 

The triggers were created around boot time, so that no users were on the
system.  A rate of growth example is a test of 240 SELECTs and noting growth
via the 'top' utility from 10 megabyte resident and 14 megabyte overall
size, to 18 megabytes resident, and 21 megabytes overall size in a time span
of 4:23, (four minutes and 23 seconds).  At about 34 megabytes, the selects
are happening so painfully slowly, that no useful work is being done. An
eyeball account would be 2 to 3 results per second, degrading to 1 result
per 45 seconds.

 

On non-triggered distributed files, the memory overall size never exceeds 13
megabytes, and indeed decreases in size in some instances, and the
performance never varies in the indexed search speed. 

 

I'd really appreciate your comments or questions.

 

Thanks,

john reid

 



This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately. 
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to