> On Wed, 7 Jul 2004 18:28:45 +0100, <[EMAIL PROTECTED]> said:
holger> Unfortunately my table could return far more than 120 rows and
holger> I am afraid this n-squared behaviour will bring my processor
holger> to it's knees. Well, I guess I just have to live with it.
1) make sure you are usi
> From: Dave Shield
> Sent: 09 July 2004 09:38
> > The data I am accessing is in a shared memory area. It is
> > already ordered but might have gaps in it (ie. some rows
> > might be missing).
>
> The gaps are no problem, but the iterator helper doesn't
> assume that the list is sorted properl
> The data I am accessing is in a shared memory area. It is already ordered
> but might have gaps in it (ie. some rows might be missing).
The gaps are no problem, but the iterator helper doesn't assume that the
list is sorted properly, so will look through the whole thing for each
individual reque
On Thu, 8 Jul 2004 08:48:37 +0100 [EMAIL PROTECTED] wrote:
HKC> > If you don't mind caching, then the stash cache helper would help.
HKC> > There a lots of different ways of optimizing, using various
HKC> > different handlers
HKC> > and helpers. It just depends on your data, and how much extra
HK
> From: Robert Story (Users)
> Sent: 08 July 2004 01:25
>
> On Wed, 7 Jul 2004 18:28:45 +0100 holger wrote:
> HKC> > I have coded my own MIB module based on a stub file that was
> HKC> > originally auto-generated by mib2c using mib2c.iterate.conf,v
> HKC> > 5.5. The module contains a table with
On Wed, 7 Jul 2004 18:28:45 +0100 [EMAIL PROTECTED] wrote:
HKC> > I have coded my own MIB module based on a stub file that was
HKC> > originally auto-generated by mib2c using mib2c.iterate.conf,v
HKC> > 5.5. The module contains a table with 7 columns and currently
HKC> > 120 rows. [...] I was qu
> From: Holger
> Sent: 06 July 2004 21:31
> I have coded my own MIB module based on a stub file that was
> originally auto-generated by mib2c using mib2c.iterate.conf,v
> 5.5. The module contains a table with 7 columns and currently
> 120 rows. The first 3 columns are table indexes and defined
Hi,
I have coded my own MIB module based on a stub file that was originally auto-generated
by mib2c using mib2c.iterate.conf,v 5.5. The module contains a table with 7 columns
and currently 120 rows. The first 3 columns are table indexes and defined as
not-accessible. The table seems to be worki
