|
JJW wrote: > > We recently had IBM do an analysis of some of our most > used programs in terms of CPU usage. One of the things > they mentioned was that %trim was a big user of CPU. Has > anyone heard this about %trim before? > %trim searches from both ends of the string to find the non-blank data. If the string is long and the data is short, repeated trimming can involve a lot of searching. To eliminate most of your trims -and- make your code nicer, consider using varying length fields, or at least varying length temporaries. When using varying fields, you normally only have to do at most one trim to get trimmed data into the field in the first place.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.