AWS Thinkbox Discussion Forums

loading partitions

not sure if this a bug or not,
at work when we load prts, adding one file, works, then it asks you to add the partition, if you hit yes, we have to wait 5minutes on that screen in order to be able to click anything, and hit ok,

if we hit NO, dont add other partitions go back to prt loader, then click add files again, this time hitting yes will be zero delay response time

weird

Sounds like infrastructure-related. The dialog that opens has to check the network (or whatever the location is) to figure out what sequences exist there.
I suspect you have Linux network with some Windows plugged in for Max/Krakatoa. Do you have the same behavior if the data is on the local workstation?

I can add some debug prints around that dialog to figure out where the time goes…

I looked at the code.

It looks at the file name to see if it is a partition and if it is, it asks the question if you want to load them all.
If you say yes, it produces a list of all possible partitions according to the file signature (e.g. if it was part02of42, it will prepare to load all 42 sequences).
Then it opens the dialog and in the dialog on open handler, it calls a function that populates the list. In this function, it does

mlb_partitionsToLoad.items = for o in Krakatoa_PRTLoader_AllNewPartitions collect (if doesFileExist o then o else o + " [NOT FOUND]")

Now if the file o in on the network, each call to doesFileExist() will have to hit the network to check the file. On Windows, if you do this once, that info usually gets cached and a second opening of the dialog would be much faster. Not sure if this is related.

What I can do is make the check for existing partitions optional - the list would populate very fast, but then you wouldn’t be able to filter which partitions actually exist on disk and which haven’t been saved yet.

Privacy | Site terms | Cookie preferences