question

Rahul R avatar image
0 Likes"
Rahul R asked Phil BoBo edited

Index on storage slots to help speed up find slot query

Hello,

I have find slot activity that gets hit a huge number of times. I use labels bayID, levelID, and slot.storageObject. Can these be indexed?

1684334651432.png

@Felix Möhlmann : A follow up to previous question on indexing for storage systems, but asking separately.

FlexSim 22.2.4
storage systemsql queryslot labelsindexing
1684334651432.png (19.6 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Phil BoBo edited

No you should not add the address scheme's slot attributes as slot labels - they will override the address scheme values.

I think also that you should be referring to the indexed labels without the slot and item prefix otherwise you will not get the benefit of the indexing system. Take a look at the description of findSlot towards the bottom where it refers to the difference between

WHERE SKU = 5

and

WHERE slot.SKU = 5
· 2
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Rahul R avatar image Rahul R commented ·

Can you pls explain this part further? "No you should not add the address scheme's slot attributes as slot labels - they will override the address scheme values."

0 Likes 0 ·
Jason Lightfoot avatar image Jason Lightfoot ♦♦ Rahul R commented ·

The address scheme will create levelID as attributes. If you're using the address scheme and set labels using the levelID they would need to be set to match since when you access slot.levelID it will look at the label first and not the address scheme value. You can test this by just running a simple query against the storage system with a rack that uses the address scheme:

Storage.system.querySlots("WHERE slot.levelID=1",0)

run that before adding your slot label 'levelID' and you will see you get the level one slots returned while afterwards you get no slots returned.


You could add labels for myLevelID and myBayID which you set yourself based on the address scheme values, and then use those without the slot prefix, which may be faster - I'm not sure anyone has tested that.

0 Likes 0 ·