Size of Mappings Tables

This topic has 3 replies, 4 voices, and was last updated 12 years, 7 months ago by Ben Michael.

Creator

Topic
April 19, 2007 at 4:50 pm #49220

Josh Stanek
Participant

Hello! I have a general question regarding the size of mapping tables and cloverleaf performance. We don’t have that many tables currently and the ones we do have are quite small. However, there is an upcoming project that could have 1200+ mappings in one table. We are concerned that performance within cloverleaf may take a hit because of this table.

Can anyone comment on this one way or another? Is there any documentation to back this up?

Thank you in advance!

JS
Creator

Topic

Viewing 2 reply threads

Author

Replies
- April 19, 2007 at 6:18 pm #61144
  
  Steve Carter
  Participant
  
  I can’t say what the limit may be for a lookup table, but I have a table with over 5200 entries. I haven’t seen any significant hit to processing due to the size.
  
  Steve
- April 19, 2007 at 6:29 pm #61145
  
  John Mercogliano
  Participant
  
  I just recently implemented a multum to FDB allergen table with over 12393 entries. Doing a backload I had no problem process 15 messages a second with no queueing.
  
  John Mercogliano
  Sentara Healthcare
  Hampton Roads, VA
- February 21, 2012 at 7:42 am #61146
  
  Ben Michael
  Participant
  
  SQLite is a good option for this.
  
  I had a 70mb table that was way to big for .tbl or a .csv lookup.
  
  Ended up going with SQLite which slowed down translation initially but then when I configured the value I was searching on as the primary key and with an index, 20 transactions processed at practically the same speed as what they did before the lookup was added.
Author

Replies

Viewing 2 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.