Do large numbers of groups/panoramas slow down loading time?

[seanji]

Do large numbers of groups/panoramas slow down loading time?

by seanji » Thu Feb 06, 2014 4:39 am

I am new to PTP2 RC2, am about to create a tour and was wondering if including a large numbers of groups and panoramas will slow down the tour's loading time? I have in mind 5 groups with a total of 33 panos.
Is it better to create more tours with less groups and panos to ensure faster load or doesn't it matter?
Thanks for your advise.

[benji33]

Re: Do large numbers of groups/panoramas slow down loading t

by benji33 » Thu Feb 06, 2014 9:44 am

In fact the XML will be bigger if panorama number is bigger, so the download time of xml file is bigger if file is bigger.
For instance a customer use 316 panoramas into it's tour and the load of xml take 8 to 10 seconds (black screen) on a standard ADSL connexion before the display of the player.

[mediavets]

Re: Do large numbers of groups/panoramas slow down loading t

by mediavets » Thu Feb 06, 2014 10:06 am

In fact the XML will be bigger if panorama number is bigger, so the download time of xml file is bigger if file is bigger.
For instance a customer use 316 panoramas into it's tour and the load of xml take 8 to 10 seconds (black screen) on a standard ADSL connexion before the display of the player.

What performance level would you consider to be offered by a 'standard ADSL connexion'?

[benji33]

Re: Do large numbers of groups/panoramas slow down loading t

by benji33 » Thu Feb 06, 2014 10:36 am

Around 3500 Kbps (430 Ko/sec).

Less than 2000Kbps is a very limited connection for tours.

Better ADSL connections are over 8000Kbps

[mediavets]

Re: Do large numbers of groups/panoramas slow down loading t

by mediavets » Thu Feb 06, 2014 11:06 am

Around 3500 Kbps (430 Ko/sec).

Less than 2000Kbps is a very limited connection for tours.

Better ADSL connections are over 8000Kbps

But still still not at all uncommon in many rural areas in the UK. I typically get 2000Kbps, or less, here in a village of 2000 population only 20 miles from the tech hotspot of Cambridge with it's world leading University and science parks - nicknamed 'Silicon Fen'.

Does France offer better ADSL bandwidth to rural users?
..............

I guess the majority of the world's population would be delighted were they able to get a 2000Kbps ADSL connection to the Net?

[benji33]

Re: Do large numbers of groups/panoramas slow down loading t

by benji33 » Thu Feb 06, 2014 11:17 am

No for rural it's about 1000-1500. But It's the low limit to have something "powerfull".

I often slow down my bandwith to 512K or 768k for tests but it's difficult to visualize correctly a VR in these conditions.

[klausesser]

Re: Do large numbers of groups/panoramas slow down loading t

by klausesser » Thu Feb 06, 2014 11:47 am

I am new to PTP2 RC2, am about to create a tour and was wondering if including a large numbers of groups and panoramas will slow down the tour's loading time? I have in mind 5 groups with a total of 33 panos.
Is it better to create more tours with less groups and panos to ensure faster load or doesn't it matter?
Thanks for your advise.

How many "scenes" you have in a tour basically doesn´t affect loading-speed when you use multires (ok - aside from reading the tour.xml on start . . ) It would of course if it would be needed to load down all the content first before you can start.
But because only the parts need to be transmitted which you actually see on-screen it doesn´t matter too much how much scenes you have in the tour.
I tested it via my iPhone`s cell-phone conection - open and view a tour with 34 scenes was the same speed as a mini-tour of 3 scenes.

MUCH influence has the kind of compression you use in PTP. I use JPG 7 for having a good compromise of data-size and speed versus quality. 9 or 10 makes some difference - but it´s a hardly visible improvement and produces much more data to transmit . .

best, Klaus

[mediavets]

Re: Do large numbers of groups/panoramas slow down loading t

by mediavets » Thu Feb 06, 2014 11:57 am

How many "scenes" you have in a tour basically doesn´t affect loading-speed when you use multires (ok - aside from reading the tour.xml on start . . ) It would of course if it would be needed to load down all the content first before you can start.
But because only the parts need to be transmitted which you actually see on-screen it doesn´t matter too much how much scenes you have in the tour.
I tested it via my iPhone`s cell-phone conection - open and view a tour with 34 scenes was the same speed as a mini-tour of 3 scenes.

MUCH influence has the kind of compression you use in PTP. I use JPG 7 for having a good compromise of data-size and speed versus quality. 9 or 10 makes some difference - but it´s a hardly visible improvement and produces much more data to transmit . .

best, Klaus

Use of video and audio content can have a major impact.

[klausesser]

Re: Do large numbers of groups/panoramas slow down loading t

by klausesser » Thu Feb 06, 2014 2:16 pm

How many "scenes" you have in a tour basically doesn´t affect loading-speed when you use multires (ok - aside from reading the tour.xml on start . . ) It would of course if it would be needed to load down all the content first before you can start.
But because only the parts need to be transmitted which you actually see on-screen it doesn´t matter too much how much scenes you have in the tour.
I tested it via my iPhone`s cell-phone conection - open and view a tour with 34 scenes was the same speed as a mini-tour of 3 scenes.

MUCH influence has the kind of compression you use in PTP. I use JPG 7 for having a good compromise of data-size and speed versus quality. 9 or 10 makes some difference - but it´s a hardly visible improvement and produces much more data to transmit . .

best, Klaus

Use of video and audio content can have a major impact.

Of course - that´s another case.

Klaus

[benji33]

Re: Do large numbers of groups/panoramas slow down loading t

by benji33 » Thu Feb 06, 2014 3:28 pm

Yes mp3 preload must be check to avoid "blocking" tiles download on startup.