Complex Table Limitation

[Former Member]

Hi all,

We are trying to high limit, max rows on SMP 3.0 Agentry Complex Table, and we reached 2 Million data rows by incrementing the Java heap size, we are doing this on Android device that have 1GB RAM, and our plan to get, up to 5 Millions data rows, is there any advice gives us, also optimization tips, for both server and client size ?

Thanks in advance.

Murat

[Former Member · Accepted solution]

See:

Just keep in mind the amount of space that one table would need just for the table rows and indexes would be:
4 Bytes * # of indexes * number of rows = Base table size

So if you have 3 indexes
4 * 3 * 5000000 = 60000000 aka 60 mb

Any time you would need to a look up onto this table would be slow because how many rows the client would have go through for it.

It would be better to break it up into a smaller tables then just 1 large table.

[bill_froelich]

The real question that needs to be asked is WHY do you fell you need 2 millions rows of data in one table on a mobile device?  The intent of an Agentry mobile application is to only have the data needed to do the job not to replicate your entire backend data structure on the mobile device. 

You should be applying filters and restricting and limited the number of rows rather than trying to increase capacity to put this much data on a mobile device in my opinion.  Plus the transmit time to perform this load will most likely be very slow and unacceptable to the users.

--Bill