I have made a virtual tour with only 14 different photos with the old version of krpano: i have used the loadpano() action; now i think is best to use the scene

with lots of panoramas, I would advise using seperate xml with clear names.

The shared interface, control, contextmenu, and other settings that wont alter per location, you put in a global.xml

the photo xml, would have their own hotspot (with a shared hotspot style in global.xml), own view and own image settings.

If you have, for instance, 5 locations sharing 1 floorplan/map, and another 5 locations share another. You can bunch up those 5 as scenes, and put them in 1 xml, while the others have their own xml (just remember when to loadscene and when to loadpano).

In the end, it doesnt really matter. An xml is only 15-30kb. And a photo is easily a couple of mb's to 10's of mb's. But the last thing you want is, the user has to wait 3 secs while staring a blank screen because the xml hasnt been loaded (and krpano couldnt load the panorama yet, because that information is in the xml). I think the golden rule used to be, max 3 seconds waittime before 50% of users click the page away. So you have to calculate what the avg dl speed is in your country. In the netherlands, I think we avg out at 10mbit (1.1mb/s). Alsoo you have to take account of the parsing time of the panorama on slow pc's. which is hard to measure. You could perhaps send google analytics events when onxmlcomplete triggers and when onpreviewcomplete/onloadcomplete triggers.