You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by Jaime Balbino <ja...@edulivre.net> on 2013/03/13 23:41:09 UTC
"2.1RC1 very slow until the login screen"
Hello,
I found the Om 2.1RC1 painfully slow to arrive the home screen to login. Was
above 60 seconds. The plugin for Moodle also came to deny access by
high waiting
time: "Operation timed out after 30000 milliseconds ..."
I then changed some variables in red5.properties:
Cut in half the values of:
rtmp.ping_interval
rtmp.max_inactivity
rtmpt.ping_interval
rtmpt.max_inactivity
1/4 cut values
rtmp.max_handshake_time
rtmpt.max_handshake_time
Adjusted values:
rtmp.default_client_bandwidth = 5000000 [less than 1Mb / s]
rtmp.default_server_bandwidth = 100000000 [bandwidth offered by my server]
The input time was reduced to 18 seconds. Now are exact only 10
seconds of white
screen until the blue loading bar.
I made a correct procedure? Can I consider these settings to other servers
as standard procedure and for the community?
Jaime Balbino
PS: OpenMeetins Network Tests not run in this RC1.
Re: "2.1RC1 very slow until the login screen"
Posted by Jaime Balbino <ja...@gmail.com>.
@Maxim,
My host initialer buy me in blocked streaming plan. Two day after they fix
this. Really the delay in OM was port 1935 blocked until the fallback port.
Thanks very much.
Jaime Balbino
For me
2013/3/13 Jaime Balbino <ja...@gmail.com>
> @Maxim and @Seba,
> Thanks the attention.
> Well .. I I returned the file red5.properties to the original settings and
> the load time was 15 seconds (!) and not more than 60 seconds as before.
> I think it was a failure in the hosting network configuration of my new
> server, and it lasted two days. My hosting did not inform me of the
> problem.
> Incidentally, today when I changed the file red5.properties this network
> failure had been corrected. Maybe DNS propagation too.
>
> For curiosity, follow the links to measure the load time on the same type
> of hosting service:
>
> OpenMeetings 2.0 build # 301 (dez/2012)
> http://http://217.172.188.16 (host in Europe)
>
> OpenMeetings 2.1RC1
> http://199.217.118.207:5080 (host in USA)
>
> Please, tell me load time for you. In Brazil is 15 seconds.
> This servers are Debian 6 and bandwidth is 100 Mb/s.
>
> Thanks,
> Jaime Balbino
>
>
> 2013/3/13 Maxim Solodovnik <so...@gmail.com>
>
>> in 2.1 you also can try "network testing tool" available from login screen
>> ant top menu inside OM
>>
>>
>> On Thu, Mar 14, 2013 at 7:39 AM, Maxim Solodovnik <solomax666@gmail.com
>> >wrote:
>>
>> > sure
>> > It would be nice if you can send 2 links
>> > 2.1 and 2.0
>> > Are you experiencing lond delay with
>> http://demo.dataved.ru/openmeetings?
>> >
>> >
>> >
>> > On Thu, Mar 14, 2013 at 7:31 AM, Jaime Balbino <jaimebalb@gmail.com
>> >wrote:
>> >
>> >> 2013/3/13 Maxim Solodovnik <so...@gmail.com>
>> >>
>> >> > long delays might be caused by
>> >> > 1) long download time of flash (~1.5M)
>> >> >
>> >> Like I said, I have other servers on the same terms (same hosting
>> type)
>> >> and without this problem.
>> >>
>> >> 2) firewall issue (port 1935 is closed, time to use fallback port
>> depends
>> >> > on you network settings)
>> >> >
>> >> In server this ports are open. In client too. My test occour in two
>> >> country
>> >> (two different routers): Brazil and Bolivia.
>> >>
>> >> I will now return the default values in the file red5.properties and
>> >> provide
>> >> the link from the server to your evaluation time of entry.
>> >> I would like to understand what is happening and why the changes I made
>> >> worked
>> >> immediately.
>> >>
>> >> Thanks,
>> >> Jaime Balbino
>> >>
>> >>
>> >>
>> >> >
>> >> >
>> >> > On Thu, Mar 14, 2013 at 6:24 AM, Jaime Balbino <ja...@gmail.com>
>> >> > wrote:
>> >> >
>> >> > > Seba
>> >> > > I have two other installations OM 2.0 on the same setup and hosting
>> >> type
>> >> > > and no long delay to enter. The time of them is 30 seconds. On a
>> >> Brazil
>> >> > > server I have another OM 2.0 also takes 30 seconds.
>> >> > > So I thought relevant report this case. I tried several actions
>> before
>> >> > > changing the file red5.properties and finally gain in reducing the
>> >> load
>> >> > > time
>> >> > > . But I have not found it documented. I also wanted to know the
>> reason
>> >> > > why charging
>> >> > > time has increased so much.
>> >> > >
>> >> > > Jaime Balbino
>> >> > >
>> >> > >
>> >> > > 2013/3/13 seba.wagner@gmail.com <se...@gmail.com>
>> >> > >
>> >> > > > Sorry but this does not seem to be reproducible,
>> >> > > > at least for me locally.
>> >> > > >
>> >> > > > Are there any similar reports out there?
>> >> > > >
>> >> > > > Sebastian
>> >> > > >
>> >> > > >
>> >> > > > 2013/3/14 Jaime Balbino <ja...@edulivre.net>
>> >> > > >
>> >> > > > > Hello,
>> >> > > > > I found the Om 2.1RC1 painfully slow to arrive the home screen
>> to
>> >> > > login.
>> >> > > > > Was
>> >> > > > > above 60 seconds. The plugin for Moodle also came to deny
>> access
>> >> by
>> >> > > > > high waiting
>> >> > > > > time: "Operation timed out after 30000 milliseconds ..."
>> >> > > > >
>> >> > > > > I then changed some variables in red5.properties:
>> >> > > > >
>> >> > > > > Cut in half the values of:
>> >> > > > > rtmp.ping_interval
>> >> > > > > rtmp.max_inactivity
>> >> > > > > rtmpt.ping_interval
>> >> > > > > rtmpt.max_inactivity
>> >> > > > >
>> >> > > > > 1/4 cut values
>> >> > > > > rtmp.max_handshake_time
>> >> > > > > rtmpt.max_handshake_time
>> >> > > > >
>> >> > > > > Adjusted values:
>> >> > > > > rtmp.default_client_bandwidth = 5000000 [less than 1Mb / s]
>> >> > > > > rtmp.default_server_bandwidth = 100000000 [bandwidth offered
>> by my
>> >> > > > server]
>> >> > > > >
>> >> > > > > The input time was reduced to 18 seconds. Now are exact only 10
>> >> > > > > seconds of white
>> >> > > > > screen until the blue loading bar.
>> >> > > > >
>> >> > > > > I made a correct procedure? Can I consider these settings to
>> other
>> >> > > > servers
>> >> > > > > as standard procedure and for the community?
>> >> > > > >
>> >> > > > > Jaime Balbino
>> >> > > > >
>> >> > > > > PS: OpenMeetins Network Tests not run in this RC1.
>> >> > > > >
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > > --
>> >> > > > Sebastian Wagner
>> >> > > > https://twitter.com/#!/dead_lock
>> >> > > > http://www.webbase-design.de
>> >> > > > http://www.wagner-sebastian.com
>> >> > > > seba.wagner@gmail.com
>> >> > > >
>> >> > >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > WBR
>> >> > Maxim aka solomax
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>> >
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
Re: "2.1RC1 very slow until the login screen"
Posted by Jaime Balbino <ja...@gmail.com>.
@Maxim and @Seba,
Thanks the attention.
Well .. I I returned the file red5.properties to the original settings and
the load time was 15 seconds (!) and not more than 60 seconds as before.
I think it was a failure in the hosting network configuration of my new
server, and it lasted two days. My hosting did not inform me of the problem.
Incidentally, today when I changed the file red5.properties this network
failure had been corrected. Maybe DNS propagation too.
For curiosity, follow the links to measure the load time on the same
type of hosting
service:
OpenMeetings 2.0 build # 301 (dez/2012)
http://http://217.172.188.16 (host in Europe)
OpenMeetings 2.1RC1
http://199.217.118.207:5080 (host in USA)
Please, tell me load time for you. In Brazil is 15 seconds.
This servers are Debian 6 and bandwidth is 100 Mb/s.
Thanks,
Jaime Balbino
2013/3/13 Maxim Solodovnik <so...@gmail.com>
> in 2.1 you also can try "network testing tool" available from login screen
> ant top menu inside OM
>
>
> On Thu, Mar 14, 2013 at 7:39 AM, Maxim Solodovnik <solomax666@gmail.com
> >wrote:
>
> > sure
> > It would be nice if you can send 2 links
> > 2.1 and 2.0
> > Are you experiencing lond delay with http://demo.dataved.ru/openmeetings
> ?
> >
> >
> >
> > On Thu, Mar 14, 2013 at 7:31 AM, Jaime Balbino <jaimebalb@gmail.com
> >wrote:
> >
> >> 2013/3/13 Maxim Solodovnik <so...@gmail.com>
> >>
> >> > long delays might be caused by
> >> > 1) long download time of flash (~1.5M)
> >> >
> >> Like I said, I have other servers on the same terms (same hosting type)
> >> and without this problem.
> >>
> >> 2) firewall issue (port 1935 is closed, time to use fallback port
> depends
> >> > on you network settings)
> >> >
> >> In server this ports are open. In client too. My test occour in two
> >> country
> >> (two different routers): Brazil and Bolivia.
> >>
> >> I will now return the default values in the file red5.properties and
> >> provide
> >> the link from the server to your evaluation time of entry.
> >> I would like to understand what is happening and why the changes I made
> >> worked
> >> immediately.
> >>
> >> Thanks,
> >> Jaime Balbino
> >>
> >>
> >>
> >> >
> >> >
> >> > On Thu, Mar 14, 2013 at 6:24 AM, Jaime Balbino <ja...@gmail.com>
> >> > wrote:
> >> >
> >> > > Seba
> >> > > I have two other installations OM 2.0 on the same setup and hosting
> >> type
> >> > > and no long delay to enter. The time of them is 30 seconds. On a
> >> Brazil
> >> > > server I have another OM 2.0 also takes 30 seconds.
> >> > > So I thought relevant report this case. I tried several actions
> before
> >> > > changing the file red5.properties and finally gain in reducing the
> >> load
> >> > > time
> >> > > . But I have not found it documented. I also wanted to know the
> reason
> >> > > why charging
> >> > > time has increased so much.
> >> > >
> >> > > Jaime Balbino
> >> > >
> >> > >
> >> > > 2013/3/13 seba.wagner@gmail.com <se...@gmail.com>
> >> > >
> >> > > > Sorry but this does not seem to be reproducible,
> >> > > > at least for me locally.
> >> > > >
> >> > > > Are there any similar reports out there?
> >> > > >
> >> > > > Sebastian
> >> > > >
> >> > > >
> >> > > > 2013/3/14 Jaime Balbino <ja...@edulivre.net>
> >> > > >
> >> > > > > Hello,
> >> > > > > I found the Om 2.1RC1 painfully slow to arrive the home screen
> to
> >> > > login.
> >> > > > > Was
> >> > > > > above 60 seconds. The plugin for Moodle also came to deny access
> >> by
> >> > > > > high waiting
> >> > > > > time: "Operation timed out after 30000 milliseconds ..."
> >> > > > >
> >> > > > > I then changed some variables in red5.properties:
> >> > > > >
> >> > > > > Cut in half the values of:
> >> > > > > rtmp.ping_interval
> >> > > > > rtmp.max_inactivity
> >> > > > > rtmpt.ping_interval
> >> > > > > rtmpt.max_inactivity
> >> > > > >
> >> > > > > 1/4 cut values
> >> > > > > rtmp.max_handshake_time
> >> > > > > rtmpt.max_handshake_time
> >> > > > >
> >> > > > > Adjusted values:
> >> > > > > rtmp.default_client_bandwidth = 5000000 [less than 1Mb / s]
> >> > > > > rtmp.default_server_bandwidth = 100000000 [bandwidth offered by
> my
> >> > > > server]
> >> > > > >
> >> > > > > The input time was reduced to 18 seconds. Now are exact only 10
> >> > > > > seconds of white
> >> > > > > screen until the blue loading bar.
> >> > > > >
> >> > > > > I made a correct procedure? Can I consider these settings to
> other
> >> > > > servers
> >> > > > > as standard procedure and for the community?
> >> > > > >
> >> > > > > Jaime Balbino
> >> > > > >
> >> > > > > PS: OpenMeetins Network Tests not run in this RC1.
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > > Sebastian Wagner
> >> > > > https://twitter.com/#!/dead_lock
> >> > > > http://www.webbase-design.de
> >> > > > http://www.wagner-sebastian.com
> >> > > > seba.wagner@gmail.com
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > WBR
> >> > Maxim aka solomax
> >> >
> >>
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>
Re: "2.1RC1 very slow until the login screen"
Posted by Maxim Solodovnik <so...@gmail.com>.
in 2.1 you also can try "network testing tool" available from login screen
ant top menu inside OM
On Thu, Mar 14, 2013 at 7:39 AM, Maxim Solodovnik <so...@gmail.com>wrote:
> sure
> It would be nice if you can send 2 links
> 2.1 and 2.0
> Are you experiencing lond delay with http://demo.dataved.ru/openmeetings?
>
>
>
> On Thu, Mar 14, 2013 at 7:31 AM, Jaime Balbino <ja...@gmail.com>wrote:
>
>> 2013/3/13 Maxim Solodovnik <so...@gmail.com>
>>
>> > long delays might be caused by
>> > 1) long download time of flash (~1.5M)
>> >
>> Like I said, I have other servers on the same terms (same hosting type)
>> and without this problem.
>>
>> 2) firewall issue (port 1935 is closed, time to use fallback port depends
>> > on you network settings)
>> >
>> In server this ports are open. In client too. My test occour in two
>> country
>> (two different routers): Brazil and Bolivia.
>>
>> I will now return the default values in the file red5.properties and
>> provide
>> the link from the server to your evaluation time of entry.
>> I would like to understand what is happening and why the changes I made
>> worked
>> immediately.
>>
>> Thanks,
>> Jaime Balbino
>>
>>
>>
>> >
>> >
>> > On Thu, Mar 14, 2013 at 6:24 AM, Jaime Balbino <ja...@gmail.com>
>> > wrote:
>> >
>> > > Seba
>> > > I have two other installations OM 2.0 on the same setup and hosting
>> type
>> > > and no long delay to enter. The time of them is 30 seconds. On a
>> Brazil
>> > > server I have another OM 2.0 also takes 30 seconds.
>> > > So I thought relevant report this case. I tried several actions before
>> > > changing the file red5.properties and finally gain in reducing the
>> load
>> > > time
>> > > . But I have not found it documented. I also wanted to know the reason
>> > > why charging
>> > > time has increased so much.
>> > >
>> > > Jaime Balbino
>> > >
>> > >
>> > > 2013/3/13 seba.wagner@gmail.com <se...@gmail.com>
>> > >
>> > > > Sorry but this does not seem to be reproducible,
>> > > > at least for me locally.
>> > > >
>> > > > Are there any similar reports out there?
>> > > >
>> > > > Sebastian
>> > > >
>> > > >
>> > > > 2013/3/14 Jaime Balbino <ja...@edulivre.net>
>> > > >
>> > > > > Hello,
>> > > > > I found the Om 2.1RC1 painfully slow to arrive the home screen to
>> > > login.
>> > > > > Was
>> > > > > above 60 seconds. The plugin for Moodle also came to deny access
>> by
>> > > > > high waiting
>> > > > > time: "Operation timed out after 30000 milliseconds ..."
>> > > > >
>> > > > > I then changed some variables in red5.properties:
>> > > > >
>> > > > > Cut in half the values of:
>> > > > > rtmp.ping_interval
>> > > > > rtmp.max_inactivity
>> > > > > rtmpt.ping_interval
>> > > > > rtmpt.max_inactivity
>> > > > >
>> > > > > 1/4 cut values
>> > > > > rtmp.max_handshake_time
>> > > > > rtmpt.max_handshake_time
>> > > > >
>> > > > > Adjusted values:
>> > > > > rtmp.default_client_bandwidth = 5000000 [less than 1Mb / s]
>> > > > > rtmp.default_server_bandwidth = 100000000 [bandwidth offered by my
>> > > > server]
>> > > > >
>> > > > > The input time was reduced to 18 seconds. Now are exact only 10
>> > > > > seconds of white
>> > > > > screen until the blue loading bar.
>> > > > >
>> > > > > I made a correct procedure? Can I consider these settings to other
>> > > > servers
>> > > > > as standard procedure and for the community?
>> > > > >
>> > > > > Jaime Balbino
>> > > > >
>> > > > > PS: OpenMeetins Network Tests not run in this RC1.
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Sebastian Wagner
>> > > > https://twitter.com/#!/dead_lock
>> > > > http://www.webbase-design.de
>> > > > http://www.wagner-sebastian.com
>> > > > seba.wagner@gmail.com
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>> >
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: "2.1RC1 very slow until the login screen"
Posted by Maxim Solodovnik <so...@gmail.com>.
sure
It would be nice if you can send 2 links
2.1 and 2.0
Are you experiencing lond delay with http://demo.dataved.ru/openmeetings?
On Thu, Mar 14, 2013 at 7:31 AM, Jaime Balbino <ja...@gmail.com> wrote:
> 2013/3/13 Maxim Solodovnik <so...@gmail.com>
>
> > long delays might be caused by
> > 1) long download time of flash (~1.5M)
> >
> Like I said, I have other servers on the same terms (same hosting type)
> and without this problem.
>
> 2) firewall issue (port 1935 is closed, time to use fallback port depends
> > on you network settings)
> >
> In server this ports are open. In client too. My test occour in two country
> (two different routers): Brazil and Bolivia.
>
> I will now return the default values in the file red5.properties and
> provide
> the link from the server to your evaluation time of entry.
> I would like to understand what is happening and why the changes I made
> worked
> immediately.
>
> Thanks,
> Jaime Balbino
>
>
>
> >
> >
> > On Thu, Mar 14, 2013 at 6:24 AM, Jaime Balbino <ja...@gmail.com>
> > wrote:
> >
> > > Seba
> > > I have two other installations OM 2.0 on the same setup and hosting
> type
> > > and no long delay to enter. The time of them is 30 seconds. On a Brazil
> > > server I have another OM 2.0 also takes 30 seconds.
> > > So I thought relevant report this case. I tried several actions before
> > > changing the file red5.properties and finally gain in reducing the load
> > > time
> > > . But I have not found it documented. I also wanted to know the reason
> > > why charging
> > > time has increased so much.
> > >
> > > Jaime Balbino
> > >
> > >
> > > 2013/3/13 seba.wagner@gmail.com <se...@gmail.com>
> > >
> > > > Sorry but this does not seem to be reproducible,
> > > > at least for me locally.
> > > >
> > > > Are there any similar reports out there?
> > > >
> > > > Sebastian
> > > >
> > > >
> > > > 2013/3/14 Jaime Balbino <ja...@edulivre.net>
> > > >
> > > > > Hello,
> > > > > I found the Om 2.1RC1 painfully slow to arrive the home screen to
> > > login.
> > > > > Was
> > > > > above 60 seconds. The plugin for Moodle also came to deny access by
> > > > > high waiting
> > > > > time: "Operation timed out after 30000 milliseconds ..."
> > > > >
> > > > > I then changed some variables in red5.properties:
> > > > >
> > > > > Cut in half the values of:
> > > > > rtmp.ping_interval
> > > > > rtmp.max_inactivity
> > > > > rtmpt.ping_interval
> > > > > rtmpt.max_inactivity
> > > > >
> > > > > 1/4 cut values
> > > > > rtmp.max_handshake_time
> > > > > rtmpt.max_handshake_time
> > > > >
> > > > > Adjusted values:
> > > > > rtmp.default_client_bandwidth = 5000000 [less than 1Mb / s]
> > > > > rtmp.default_server_bandwidth = 100000000 [bandwidth offered by my
> > > > server]
> > > > >
> > > > > The input time was reduced to 18 seconds. Now are exact only 10
> > > > > seconds of white
> > > > > screen until the blue loading bar.
> > > > >
> > > > > I made a correct procedure? Can I consider these settings to other
> > > > servers
> > > > > as standard procedure and for the community?
> > > > >
> > > > > Jaime Balbino
> > > > >
> > > > > PS: OpenMeetins Network Tests not run in this RC1.
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sebastian Wagner
> > > > https://twitter.com/#!/dead_lock
> > > > http://www.webbase-design.de
> > > > http://www.wagner-sebastian.com
> > > > seba.wagner@gmail.com
> > > >
> > >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>
--
WBR
Maxim aka solomax
Re: "2.1RC1 very slow until the login screen"
Posted by Jaime Balbino <ja...@gmail.com>.
2013/3/13 Maxim Solodovnik <so...@gmail.com>
> long delays might be caused by
> 1) long download time of flash (~1.5M)
>
Like I said, I have other servers on the same terms (same hosting type)
and without this problem.
2) firewall issue (port 1935 is closed, time to use fallback port depends
> on you network settings)
>
In server this ports are open. In client too. My test occour in two country
(two different routers): Brazil and Bolivia.
I will now return the default values in the file red5.properties and provide
the link from the server to your evaluation time of entry.
I would like to understand what is happening and why the changes I made worked
immediately.
Thanks,
Jaime Balbino
>
>
> On Thu, Mar 14, 2013 at 6:24 AM, Jaime Balbino <ja...@gmail.com>
> wrote:
>
> > Seba
> > I have two other installations OM 2.0 on the same setup and hosting type
> > and no long delay to enter. The time of them is 30 seconds. On a Brazil
> > server I have another OM 2.0 also takes 30 seconds.
> > So I thought relevant report this case. I tried several actions before
> > changing the file red5.properties and finally gain in reducing the load
> > time
> > . But I have not found it documented. I also wanted to know the reason
> > why charging
> > time has increased so much.
> >
> > Jaime Balbino
> >
> >
> > 2013/3/13 seba.wagner@gmail.com <se...@gmail.com>
> >
> > > Sorry but this does not seem to be reproducible,
> > > at least for me locally.
> > >
> > > Are there any similar reports out there?
> > >
> > > Sebastian
> > >
> > >
> > > 2013/3/14 Jaime Balbino <ja...@edulivre.net>
> > >
> > > > Hello,
> > > > I found the Om 2.1RC1 painfully slow to arrive the home screen to
> > login.
> > > > Was
> > > > above 60 seconds. The plugin for Moodle also came to deny access by
> > > > high waiting
> > > > time: "Operation timed out after 30000 milliseconds ..."
> > > >
> > > > I then changed some variables in red5.properties:
> > > >
> > > > Cut in half the values of:
> > > > rtmp.ping_interval
> > > > rtmp.max_inactivity
> > > > rtmpt.ping_interval
> > > > rtmpt.max_inactivity
> > > >
> > > > 1/4 cut values
> > > > rtmp.max_handshake_time
> > > > rtmpt.max_handshake_time
> > > >
> > > > Adjusted values:
> > > > rtmp.default_client_bandwidth = 5000000 [less than 1Mb / s]
> > > > rtmp.default_server_bandwidth = 100000000 [bandwidth offered by my
> > > server]
> > > >
> > > > The input time was reduced to 18 seconds. Now are exact only 10
> > > > seconds of white
> > > > screen until the blue loading bar.
> > > >
> > > > I made a correct procedure? Can I consider these settings to other
> > > servers
> > > > as standard procedure and for the community?
> > > >
> > > > Jaime Balbino
> > > >
> > > > PS: OpenMeetins Network Tests not run in this RC1.
> > > >
> > >
> > >
> > >
> > > --
> > > Sebastian Wagner
> > > https://twitter.com/#!/dead_lock
> > > http://www.webbase-design.de
> > > http://www.wagner-sebastian.com
> > > seba.wagner@gmail.com
> > >
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>
Re: "2.1RC1 very slow until the login screen"
Posted by Maxim Solodovnik <so...@gmail.com>.
long delays might be caused by
1) long download time of flash (~1.5M)
2) firewall issue (port 1935 is closed, time to use fallback port depends
on you network settings)
On Thu, Mar 14, 2013 at 6:24 AM, Jaime Balbino <ja...@gmail.com> wrote:
> Seba
> I have two other installations OM 2.0 on the same setup and hosting type
> and no long delay to enter. The time of them is 30 seconds. On a Brazil
> server I have another OM 2.0 also takes 30 seconds.
> So I thought relevant report this case. I tried several actions before
> changing the file red5.properties and finally gain in reducing the load
> time
> . But I have not found it documented. I also wanted to know the reason
> why charging
> time has increased so much.
>
> Jaime Balbino
>
>
> 2013/3/13 seba.wagner@gmail.com <se...@gmail.com>
>
> > Sorry but this does not seem to be reproducible,
> > at least for me locally.
> >
> > Are there any similar reports out there?
> >
> > Sebastian
> >
> >
> > 2013/3/14 Jaime Balbino <ja...@edulivre.net>
> >
> > > Hello,
> > > I found the Om 2.1RC1 painfully slow to arrive the home screen to
> login.
> > > Was
> > > above 60 seconds. The plugin for Moodle also came to deny access by
> > > high waiting
> > > time: "Operation timed out after 30000 milliseconds ..."
> > >
> > > I then changed some variables in red5.properties:
> > >
> > > Cut in half the values of:
> > > rtmp.ping_interval
> > > rtmp.max_inactivity
> > > rtmpt.ping_interval
> > > rtmpt.max_inactivity
> > >
> > > 1/4 cut values
> > > rtmp.max_handshake_time
> > > rtmpt.max_handshake_time
> > >
> > > Adjusted values:
> > > rtmp.default_client_bandwidth = 5000000 [less than 1Mb / s]
> > > rtmp.default_server_bandwidth = 100000000 [bandwidth offered by my
> > server]
> > >
> > > The input time was reduced to 18 seconds. Now are exact only 10
> > > seconds of white
> > > screen until the blue loading bar.
> > >
> > > I made a correct procedure? Can I consider these settings to other
> > servers
> > > as standard procedure and for the community?
> > >
> > > Jaime Balbino
> > >
> > > PS: OpenMeetins Network Tests not run in this RC1.
> > >
> >
> >
> >
> > --
> > Sebastian Wagner
> > https://twitter.com/#!/dead_lock
> > http://www.webbase-design.de
> > http://www.wagner-sebastian.com
> > seba.wagner@gmail.com
> >
>
--
WBR
Maxim aka solomax
Re: "2.1RC1 very slow until the login screen"
Posted by Jaime Balbino <ja...@gmail.com>.
Seba
I have two other installations OM 2.0 on the same setup and hosting type
and no long delay to enter. The time of them is 30 seconds. On a Brazil
server I have another OM 2.0 also takes 30 seconds.
So I thought relevant report this case. I tried several actions before
changing the file red5.properties and finally gain in reducing the load time
. But I have not found it documented. I also wanted to know the reason
why charging
time has increased so much.
Jaime Balbino
2013/3/13 seba.wagner@gmail.com <se...@gmail.com>
> Sorry but this does not seem to be reproducible,
> at least for me locally.
>
> Are there any similar reports out there?
>
> Sebastian
>
>
> 2013/3/14 Jaime Balbino <ja...@edulivre.net>
>
> > Hello,
> > I found the Om 2.1RC1 painfully slow to arrive the home screen to login.
> > Was
> > above 60 seconds. The plugin for Moodle also came to deny access by
> > high waiting
> > time: "Operation timed out after 30000 milliseconds ..."
> >
> > I then changed some variables in red5.properties:
> >
> > Cut in half the values of:
> > rtmp.ping_interval
> > rtmp.max_inactivity
> > rtmpt.ping_interval
> > rtmpt.max_inactivity
> >
> > 1/4 cut values
> > rtmp.max_handshake_time
> > rtmpt.max_handshake_time
> >
> > Adjusted values:
> > rtmp.default_client_bandwidth = 5000000 [less than 1Mb / s]
> > rtmp.default_server_bandwidth = 100000000 [bandwidth offered by my
> server]
> >
> > The input time was reduced to 18 seconds. Now are exact only 10
> > seconds of white
> > screen until the blue loading bar.
> >
> > I made a correct procedure? Can I consider these settings to other
> servers
> > as standard procedure and for the community?
> >
> > Jaime Balbino
> >
> > PS: OpenMeetins Network Tests not run in this RC1.
> >
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
Re: "2.1RC1 very slow until the login screen"
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Sorry but this does not seem to be reproducible,
at least for me locally.
Are there any similar reports out there?
Sebastian
2013/3/14 Jaime Balbino <ja...@edulivre.net>
> Hello,
> I found the Om 2.1RC1 painfully slow to arrive the home screen to login.
> Was
> above 60 seconds. The plugin for Moodle also came to deny access by
> high waiting
> time: "Operation timed out after 30000 milliseconds ..."
>
> I then changed some variables in red5.properties:
>
> Cut in half the values of:
> rtmp.ping_interval
> rtmp.max_inactivity
> rtmpt.ping_interval
> rtmpt.max_inactivity
>
> 1/4 cut values
> rtmp.max_handshake_time
> rtmpt.max_handshake_time
>
> Adjusted values:
> rtmp.default_client_bandwidth = 5000000 [less than 1Mb / s]
> rtmp.default_server_bandwidth = 100000000 [bandwidth offered by my server]
>
> The input time was reduced to 18 seconds. Now are exact only 10
> seconds of white
> screen until the blue loading bar.
>
> I made a correct procedure? Can I consider these settings to other servers
> as standard procedure and for the community?
>
> Jaime Balbino
>
> PS: OpenMeetins Network Tests not run in this RC1.
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com