You did a great benchmark, Gerog. That's really cool.
It really highlights some fact that I was aware of but not sure about their influence :
- Each jpeg file contains also a header, that doesn't stores anything usefull ( pixels in fact ).
So more tiles, more unneeded stuff to download ( see 139 mb versus 36.7 mb for small / high res tile version ).
So apparently, this simple fact compensate what you could gain in hidden pixels frame download.
- Another fact to take into account : if you have 10 big images to download through the web, you have less chance to be stucked waiting for one to finish than if you have 150 small images to download ( each if we consider that the size to download of 10 big images = size of 150 small images ). That's a typical behavior of internet routine.
So it seems that the conclusion is clear : the bigger the best !
( where does that comes from ?
to be honest - im unhappy with what you're saying...
... because it leads me to conclusion that using other value than the suggested one is useless. So why having this option at all?
If I have a pano source of 20.000x10.000 pixsel sliced into 64pixel tiles and I've a 5000x2000 source pano sliced into 64 pixel tiles...
and there is no speed difference in loading (compared to the fast loading versions with 1200 cutting size)?
139mb contra 36.7mb is of course more to download. But if you look into the created directory you see the 64cutting version does have one more subfolder than the 128cutting version with 36.7mb (2more subfolders than the 300cutting version etc.). if you compare the equal directories of both version they're equal in size.
So If I load initial panoview of the 64cuttingsize version, why must the version be downloaded with the biggest number of slices (more files more overhead, more mb etc.= longer loading), I did not zoom into the pano so the smallest of the subfolders containing only the 6 tiles should be enough to be downloaded for displaying. If I zoom later into the pano according to my choosen area, exactly than the needed data from the according subfolder should be loaded & displayed. Finally if I zoom into the pono to the maximum the tiles of that directory containing the most tiles should be loaded according to my choosen area).
PS: and using only big cuttingsize values results in having only view subdirectories with less multiresolution versions