Table vs hashtable

[Arhowk]

I've seen people saying that you should use Table so that theres only one hashtable to store information.

I've also seen people say to not store so much information to a hashtable because the more information a hashtable has, the slower the lookup times are.

With that logic, wouldn't it be smarter to use multiple hashtables rather than Table? Even though you have multiple hashtables, you have the enhanced speed of the hashtables not having as many keys.

 

[Nestharus]

only use a hashtable when you are going to have an insane amount of information or are working on a critical system and need as much speed as possible

 

[edo494]

this hardly hits performance at all, because the lookup is done on underlying level which is much faster than Jass

yes, fullier(is that even word?) hashtable == slower load, but really, this is Jass, if you fear performance drops, use array

I dont think people should be concerned by stuff like this really, mainly because many GUI spells use their own hashtables and also you have a 256 hashtables limit so if you can, you should avoid declaring multiple hashtables

 

[Arhowk]

only use a hashtable when you are going to have an insane amount of information or are working on a critical system and need as much speed as possible

define "insane" I have a full screen inventory system, talent tree, and speed quest system all running off of Table