Tokenization size and the "pig"...

[Bob Stockler]

Top post for JE . . .

I have all of my PF*TOKSIZE parameters set by default to 200000.

I don't think there is any significant penalty on filePro v4.8
or later to have them so set (I've done so for a long time).

The fact of the matter is, I think filePro v5.6 maybe oughta just
ignore these parameters and use whatever memory is needed.  (That
would be one less thing for people to be concerned with.)

I *think* the resulting processing tables use only the actual
memory they consume, so setting these parameters to 500000 would
not use any more memory than if they were set to lower values.

I think they're an anachronism (but am willing to be proven wrong).

Bob

John Esak wrote (on Mon, May 30, 2005 at 06:13:42PM -0400):

| I've put up a couple messages now about PFTOKSIZE... (maybe only one, can't
| remember). In any case, I have sent out several to people who are running
| the pig code. I've been saying that PFFORMTOKSIZE should be set to about
| 80000. That is just because this is where it was set on my freeBSD system,
| not becuase the pig code requires it. Just for grins I tried lowering it and
| lowering it to see what it really had to be in order for the "pig" CALL
| table to work. Turns out that with no other tokenization variables set at
| all, the magic number is 15872. Anything lower and no go. As I said earlier,
| there isn't any performance hit seen on most newer systems if these
| variables are set pretty high. (Newer systems in this case means those with
| standard memory levels installed. It's so cheap these days, the more the
| better, but I never even saw any performance problems on older systems with
| only 128MB of memory and umpteen users... so, it is just not a problem.) The
| filePro stuff just all works without any problems if you set these to some
| values that work for your applications. So, I still suggest 100000 for all
| three tok size variables as a good starting point for most code. Change them
| as and if you get warning messages.
| 
|   PFTOKSIZ=100000
|   PFAUTOKSIZE=100000
|   PFFORMTOKSIZE=100000
| 
| The PFFORMTOKSIZE variable is the one which governs both CALL tables _and_
| FORM processing. By FORM processing, I mean, the kind which happens when you
| press F for Print Forms and run a form that has a processing table attached
| to it. My guess is that this is the only time this variable comes into play.
| I think running an output "form" or "report" or "labels" is governed solely
| by PFTOKSIZE... and PFAUTOKSIZE if there is an automatic processing table
| involved.  I'm not dead certain about this, so Ken or someone who knows, can
| correct this if I'm wrong.
| 
| Either way, I should have put a temporary PFFORMTOKSIZE=20000 on my menu
| line in the sample system, but that would have required a menu script file,
| since I don't know the direct path to everyone's fp directory and I was
| trying to keep things simple. So, apologies to the few of you who had to set
| your PFFORMTOKSIZE up, and if you don't like setting it as high as 80000 as
| I've metnioned before... put it down to 20000. (That is, if you don't take
| my word for it that 100000 is perfectly fine! :-)
| 
| John
| Visit The FP Room www.tinyurl.com/yuag7 24/7
| 
| Take a demo ride of the "pig" at www.valar.com/single
| 
| _______________________________________________
| Filepro-list mailing list
| Filepro-list at lists.celestial.com
| http://mailman.celestial.com/mailman/listinfo/filepro-list

-- 
Bob Stockler - bob at trebor.iglou.com
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).