I've got a loopback driver that refers to a single object which has one
multi-valued attribute with several thousand values.
This attribute is specified in the driver filter and has optimize modify

[03/12/14 11:57:56.706]:Loopback PT:Reading relevant attributes from


[03/12/14 12:06:12.195]:Loopback PT:Read result:

and then the instance document with several thousand attribute values.

This is an engine function, and makes level 3 trace exceedingly slow and
somewhat useless. There should be an ECV or something to allow this to
be turned off.

I rely on the timestamp/optimize modify as I have a daily trigger job
that will remove values from this attribute at a specific interval after
they were first added to the list.
The attribute values are used with the unique-name token to generate a
name that hasn't been used before.

Anyone had to deal with similar situation and have a better solution? I
had thought of a mapping table, but was unsure if that was a better
approach (I know it's cached in memory better)

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
alexmchugh's Profile: https://forums.netiq.com/member.php?userid=461
View this thread: https://forums.netiq.com/showthread.php?t=50237