tdmcs0198m000 provides the opportunity to identify sessions that would benefit from table boosters.

As the session help does not explain what type of processing against tables would be improved, if you have experience with table boosters, I would like feedback for the following questions.

If large number of deletes are being performed against a table, is it a good candidate for being "Boosted"?

If a large number of references are being checked against a table, but the table is only read, would it be a candidate. The reference checking is not always against the same key.

Finally, I presume yes to the following.
Repeated read references to a table using the same key would benefit from the table being listed for boosting. True of false?

Did I miss any condition where the table would be placed into the booster category?

Your feedback would be most appreciated. (We have no source so we also do not know fully which tables are used by a session). (Ex. session tdpur4223m000)

Hi Leslie,

Table boosters mostly just load the table into the bshell's (or driver... don't remember) memory area, this means that if you are doing a lot of reads from a table (such as reference lookups) then you may see some benefit from the table booster.
Deletes, inserts and updates will be unaffected.

Additionally, this was really meant to help tbase/bisam.. If you're using a real database you might not see any improvement..

Dave

As Dave described, table boosters tell the bshell to cache table contents. Even though this sounds like a good idea to improve performance, here comes the catch:

This caching is done within the single bshell. So if a second bshell updates data, than the first bshell will not see the changes. Obviously this can only be good for data, which hardly changes, like lookup tables.

My personell recommendation is: Only if you are absolutely sure, that nobody will change the "boosted" tables, use it. Otherwise forget about it.


Also like Dave said: A "proper" database will do it's own caching and this works, as the database knows it's own updates.

By the way, if I am not mistaken, there is a slightly better mechnism for this in BaanERP. Here caching is done on application/server level. This way, it will work, as long as you have excactly one application server. But I am not an expert on BaanERP, so do not ask me for details here.

Enjoy

markus

Hi Les,

The Application Performance Guide that Baan put out with Baan ERP Documentation disk will give good guidence for table boosters.

Also look at the bic_info command. It will list the tables, external functions etc. of objects that can be used for zooming, overlays, etc.

Especially when using a "real" database, table boosters help to improve performance. Remember Tbase/bisam/bbase is much faster compared to e.g. Oracle and Level 1 has caching. As a fast lookup in a small cache is much faster than going over several processes it gains.

Table boosters especially gain for batch sessions. Don't expect dramatic gains, but 10% is a possible gain.

Hope this helps,
Dick