Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
In a thread on stored procedure limits, Art S. Kagel said procedures can recurse or call each other only to 16 levels, while thousands can run in different sessions. Superboer disagreed, recalling a pre-7.3 upper-case hack that went at least 256 levels deep. Another poster asked where the author of that hack now was. The limit question was not settled.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Art S. Kagel — — source: Usenet: comp.databases.informix
OptionJ wrote:
> I found a reference that tells me that Informix can only have 16 stored
> procedures running at one time.
The only thing I can think of that's remotely related is that you can only
recurse in a stored procedure, or have one proc call another, to a depth of
16 calls. You can have 1000's of procs running in different sessions
sumultaceously.
Art S. Kagel
> Currently, we have a variety of things that are set up as stored
> procedures that take a long time to process. If there are 16 running
> at one time, does that mean that the 17th must wait until one finishes
> in order to be loaded into cache so that it can start processing?
>
> I believe that we are running an older version, 7.1, of Informix. If
> this is enhanced in later versions, I'd be interested in knowing that
> as well.
>
> Many of these processes have been, in my opinion, incorrectly set up as
> SP's. If this is also causing a performance hit, then I would be
> better able to request time and resources to make these changes.
>
> Thank you!
>
> Option J Upton
>
Hello Art,
afaikr 16 deep is not true either; remember the pre7.2 hack for upper.
i thing the great Junet wrote that; it could do at least 256 deep.
Superboer.
Art S. Kagel schreef:
> OptionJ wrote:
> > I found a reference that tells me that Informix can only have 16 stored
> > procedures running at one time.
>
> The only thing I can think of that's remotely related is that you can only
> recurse in a stored procedure, or have one proc call another, to a depth of
> 16 calls. You can have 1000's of procs running in different sessions
> sumultaceously.
>
> Art S. Kagel
>
>
> > Currently, we have a variety of things that are set up as stored
> > procedures that take a long time to process. If there are 16 running
> > at one time, does that mean that the 17th must wait until one finishes
> > in order to be loaded into cache so that it can start processing?
> >
> > I believe that we are running an older version, 7.1, of Informix. If
> > this is enhanced in later versions, I'd be interested in knowing that
> > as well.
> >
> > Many of these processes have been, in my opinion, incorrectly set up as
> > SP's. If this is also causing a performance hit, then I would be
> > better able to request time and resources to make these changes.
> >
> > Thank you!
> >
> > Option J Upton
> >
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.