Optimizing large lookup tables

Thanks unRuleY -

 

 

I think I understand, but do you think that approach could be leveraged to import a large static lookup table into an array? Or is that even a good idea? My concerns center around what happens on config re-load or reboot: Is that data then gone until it is added back again? (iRule is intended to deny access unless matching data is in the list, so I don't want to create a false "site down" condition by having the list go away unexpectedly.)

 

 

My customer has a list of numeric ranges that will need to be referenced in an array. The data is static, and it is provided monthly to the customer as a table with ~3000 rows, 2 columns each, like this:27049783822704978382

 

27049783942704978394

 

27049783962704978396

 

27049784652704978465

 

27049785062704978506

 

32624734863262473486

 

32624735443262473544

 

32624735493262473549

 

32624735683262473568

 

32624735833262473583

 

32624735873262473587

 

32624736643262473664

 

32624736893262473689

 

32624737363262473736

 

32624750803262475080The tools available for class manipulation are not sufficient for this exercise, and when I try to manupulate a class as if it were an array, I get a TCL error 'can't read "::class_name(xxxx)": variable isn't array while executing "array get $::class_name(xxxx)"'

 

 

thanks for any insight or alternative approaches

 

/deb