One long list or multiple shorter ones?

[ChinRey]

This is probably extreme micro-optimization but I'm working on a texture changer for a tree. There are two different sets of textures, one set for the foliage and one for the bark. Is it better to have one long list containing all the texture names and UUIDs or a separate list for each?

[Rolig Loon]

I have done it both ways but, frankly, have never based my choice on how it might optimize the script's speed or memory allocation.  As far as I am concerned, I construct lists on the basis of how easily I can handle them without getting my brain all tangled up in index issues. If I have to write complex code to keep track of which list element is which, I am more likely to make mistakes and raise my blood pressure than  if I opt for a simpler code.  I suppose in the end that my script is "optimized" if it works accurately with minimal hassle.

[Innula Zenovka]

I think using one long list uses slightly (and I mean very slightly) less memory than using two short ones, but it's only a matter of a few bytes.  Not enough to make any significant difference.