• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • 🏆 Hive's 6th HD Modeling Contest: Mechanical is now open! Design and model a mechanical creature, mechanized animal, a futuristic robotic being, or anything else your imagination can tinker with! 📅 Submissions close on June 30, 2024. Don't miss this opportunity to let your creativity shine! Enter now and show us your mechanical masterpiece! 🔗 Click here to enter!

Full Screen Window

Status
Not open for further replies.

Dr Super Good

Spell Reviewer
Level 64
Joined
Jan 18, 2005
Messages
27,232
Unless one really needs to bulk store stuff, hashtables are probably the way to go since they are perfect for sparse storage. When it comes to the case of dozens of joined arrays, they might even perform faster.

For bulk storage you are probably stuck with joined arrays since at large numbers of elements the hashtables start to degrade from O(1) to O(n) in internal lookup complexity (people have reported they can become extremely slow).
 
Level 24
Joined
Aug 1, 2013
Messages
4,657
Xonok (I think) told me hashtables become slower the more data is inside them.
I can see why.

But where to save the data doesnt really matter.
We dont need 100% efficiency because there is not much happening at all.
What I do want to know is how I can save everything (inside hashtables for now) so I can find my objects very easily.
 
Status
Not open for further replies.
Top