Any issues with many unused spoints/qset?

Are there any issues with having an arbitrarily large and mostly unused set of spoints/qset in an EXTSEOUT run? I'm thinking of possible downstream issues.

Here's a scenario that would lead one to defining a large set of spoints/qset:

Can't use AUTOQSET

EIGRL with a frequency range

Unknown # of RESVECs

Parents

0 anthony.carlson over 5 years ago

Just a follow up note on this topic. I was doing some EXTSEOUT runs today and noted that having a very large set of spoints/qset led to slow run times. E.g. small set of spoints/qset job took 8 minutes, but when I had a large range of spoints/qsets defined (90000000 THRU 99999999) the same job with no other differences ran for more than 2 hours before I killed it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 anthony.carlson over 5 years ago

Just a follow up note on this topic. I was doing some EXTSEOUT runs today and noted that having a very large set of spoints/qset led to slow run times. E.g. small set of spoints/qset job took 8 minutes, but when I had a large range of spoints/qsets defined (90000000 THRU 99999999) the same job with no other differences ran for more than 2 hours before I killed it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data