Find the Best Demos and Examples

Check out this quick tour to find the best demos and examples for you, and to see how the Felgo SDK can help you to develop your next app or game!

Forums

OverviewFelgo 2 Support (Qt 5) › Maximum table size before long delays (1 second +) on older phones?

Tagged: 

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #19700

    Eric

    Hello,

    I have a situation in my app where I need to decide whether to keep all of a certain type of data in one table (normalized) or separating it into multiple tables. The table could get up to about 10,000 rows, or I could separate that into around 25 tables of approximately 400 rows each (the tables would be created intermittently based on user input as different types of data are added by the user). Normally I wouldn’t worry on a computer but I thought I should check if one table of 10,000 rows would cause noticible delays of a second or more on older phones when searching and returning 300-500 rows with multiple conditions.

    If multiple tables are used, data would only be pulled from one table at a time with no conditionals.

    Thank you,

    Eric

    #19706

    Marcin

    Hi,
    Base on my experience with databases, for this amount of rows it really doesn’t matter.
    Even storing this in files and using “grep” like solution would be fast enough.
    I wouldn’t worry with this amount of data.

    If you get more rows, lets 100 000 and more, then I should consider the right db engine and maybe a remote db rather than run on the user device.

Viewing 2 posts - 1 through 2 (of 2 total)

RSS feed for this thread

You must be logged in to reply to this topic.