16,000 names in a table too much?

I’m creating a part of my game that makes it seem like the user is playing against other players to give them a social kind of feel, but in reality all the users will be local on the device. I have a table with 16,000 random usernames in it and I will be pulling names at random. I’m just wondering if this is too many usernames and could there be any major memory issues with having this name names in a table?

I’ve used a few debugging tools and the memory doesn’t seem all that intense I’m just wondering if there is anything that I might not be thinking about.

Thanks

I’ve seen people do tests where a table had over 10million items in it, and it was still ok.  

But if you wanted to you could always split the names up into separate tables, and then just have one of the tables loaded at any given time.

Do you mean SQLite table? If so I think it will be no problem. 

Nope I mean a lua table. 
 

That’s not a bad idea. I might got that route actually.

16.000 entries in a lua table isn’t so bad. Let’s assume each name is 15 chars and each char is 2 bytes. We then have

15 chars * 2 bytes * 16000 names = 480kB

… plus whatever overhead comes from the table itself, which is likely significantly less than the data.

Now compare to a single 512 x 512 image:

512 pixels x 512 pixels x 4 bytes = 1 MB

Of course, it’s not quite fair to compare texture memory and system memory, but it gives an idea of the relative sizes.

I’ve seen people do tests where a table had over 10million items in it, and it was still ok.  

But if you wanted to you could always split the names up into separate tables, and then just have one of the tables loaded at any given time.

Do you mean SQLite table? If so I think it will be no problem. 

Nope I mean a lua table. 
 

That’s not a bad idea. I might got that route actually.

16.000 entries in a lua table isn’t so bad. Let’s assume each name is 15 chars and each char is 2 bytes. We then have

15 chars * 2 bytes * 16000 names = 480kB

… plus whatever overhead comes from the table itself, which is likely significantly less than the data.

Now compare to a single 512 x 512 image:

512 pixels x 512 pixels x 4 bytes = 1 MB

Of course, it’s not quite fair to compare texture memory and system memory, but it gives an idea of the relative sizes.