FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 04-24-2008, 01:14 AM
Matt Domsch
 
Default app6 up

so I'm a little late requesting permission, though I was on IRC during
the whole "ordeal" :-) so plenty of people had a chance to object. I
brought up app6 as a xen guest on telia1.fp.o in Germany. It's only
running MM's mirrorlist server right now, but all seems fine and
dandy.

--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux

_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
 
Old 04-24-2008, 02:04 AM
Toshio Kuratomi
 
Default app6 up

Matt Domsch wrote:

so I'm a little late requesting permission, though I was on IRC during
the whole "ordeal" :-) so plenty of people had a chance to object. I
brought up app6 as a xen guest on telia1.fp.o in Germany. It's only
running MM's mirrorlist server right now, but all seems fine and
dandy.

That's excellent. I wonder what the latency for requests is from
app6.... (Could make some of the things that J5 is trying to do with
myfedora even harder.)


Of course, we don't have to run apps that myfedora consumes on app6 but
it would be nice to not have to worry about physical geography when an
emergency causes us to need to bring up other applications on a
different app server.


-Toshio

_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
 
Old 04-24-2008, 02:12 AM
Matt Domsch
 
Default app6 up

On Wed, Apr 23, 2008 at 07:04:35PM -0700, Toshio Kuratomi wrote:
> Matt Domsch wrote:
> >so I'm a little late requesting permission, though I was on IRC during
> >the whole "ordeal" :-) so plenty of people had a chance to object. I
> >brought up app6 as a xen guest on telia1.fp.o in Germany. It's only
> >running MM's mirrorlist server right now, but all seems fine and
> >dandy.
> >
> That's excellent. I wonder what the latency for requests is from
> app6.... (Could make some of the things that J5 is trying to do with
> myfedora even harder.)
>
> Of course, we don't have to run apps that myfedora consumes on app6 but
> it would be nice to not have to worry about physical geography when an
> emergency causes us to need to bring up other applications on a
> different app server.

For those of us in the US, yes, it's higher. From Europe I suspect
it's faster for them than it is for us.

Typical responses when hitting app3 and app5 are in the 0.300-0.400s range.
When hitting app6 I'm seeing around 0.800s.

It's a shame mod_proxy_balancer doesn't grok geoip. It'd be fun for
it to default North American users to our US app servers, .EU to
Telia, with the fallback to use any of the others that are alive...

Anyone up for some coding? :-)

--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux

_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
 
Old 04-24-2008, 02:12 AM
Mike McGrath
 
Default app6 up

On Wed, 23 Apr 2008, Matt Domsch wrote:

> On Wed, Apr 23, 2008 at 07:04:35PM -0700, Toshio Kuratomi wrote:
> > Matt Domsch wrote:
> > >so I'm a little late requesting permission, though I was on IRC during
> > >the whole "ordeal" :-) so plenty of people had a chance to object. I
> > >brought up app6 as a xen guest on telia1.fp.o in Germany. It's only
> > >running MM's mirrorlist server right now, but all seems fine and
> > >dandy.
> > >
> > That's excellent. I wonder what the latency for requests is from
> > app6.... (Could make some of the things that J5 is trying to do with
> > myfedora even harder.)
> >
> > Of course, we don't have to run apps that myfedora consumes on app6 but
> > it would be nice to not have to worry about physical geography when an
> > emergency causes us to need to bring up other applications on a
> > different app server.
>
> For those of us in the US, yes, it's higher. From Europe I suspect
> it's faster for them than it is for us.
>
> Typical responses when hitting app3 and app5 are in the 0.300-0.400s range.
> When hitting app6 I'm seeing around 0.800s.
>
> It's a shame mod_proxy_balancer doesn't grok geoip. It'd be fun for
> it to default North American users to our US app servers, .EU to
> Telia, with the fallback to use any of the others that are alive...
>
> Anyone up for some coding? :-)
>

WE do need some metrics there though. Those numbers could be very
interesting. And I know there's tweaks to openvpn we can do.

-Mike

_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
 
Old 04-24-2008, 02:15 AM
Toshio Kuratomi
 
Default app6 up

Answering myself, ping times from app4 (phx-Arizona), app5.vpn
(tummy-Colorado), and app6.vpn(telia-Germany) to db2(phx-Arizona)


[toshio@app4 ~]$ ping db2
PING db2.fedora.phx.redhat.com (10.8.34.120) 56(84) bytes of data.
64 bytes from 10.8.34.120: icmp_seq=1 ttl=64 time=0.249 ms
64 bytes from 10.8.34.120: icmp_seq=2 ttl=64 time=0.285 ms
64 bytes from 10.8.34.120: icmp_seq=3 ttl=64 time=0.764 ms
64 bytes from 10.8.34.120: icmp_seq=4 ttl=64 time=0.280 ms

[toshio@app5 ~]$ ping db2
PING db2.vpn.fedoraproject.org (192.168.1.19) 56(84) bytes of data.
64 bytes from 192.168.1.19: icmp_seq=1 ttl=64 time=43.7 ms
64 bytes from 192.168.1.19: icmp_seq=2 ttl=64 time=42.9 ms
64 bytes from 192.168.1.19: icmp_seq=3 ttl=64 time=42.9 ms
64 bytes from 192.168.1.19: icmp_seq=4 ttl=64 time=42.9 ms

[toshio@app6 ~]$ ping db2
PING db2.vpn.fedoraproject.org (192.168.1.19) 56(84) bytes of data.
64 bytes from 192.168.1.19: icmp_seq=1 ttl=64 time=196 ms
64 bytes from 192.168.1.19: icmp_seq=2 ttl=64 time=181 ms
64 bytes from 192.168.1.19: icmp_seq=3 ttl=64 time=184 ms
64 bytes from 192.168.1.19: icmp_seq=4 ttl=64 time=186 ms

So each request from an app server in phx to the database or to another
app will be 200x faster to set up than from an app server at tummy and
nearly 1000x faster to set up than telia. If we deploy apps at telia it
will be essential to minimize the number of requests if we want to keep
things fast.


-Toshio

_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
 
Old 04-24-2008, 02:25 AM
Matt Domsch
 
Default app6 up

On Wed, Apr 23, 2008 at 07:15:59PM -0700, Toshio Kuratomi wrote:
> So each request from an app server in phx to the database or to another
> app will be 200x faster to set up than from an app server at tummy and
> nearly 1000x faster to set up than telia. If we deploy apps at telia it
> will be essential to minimize the number of requests if we want to keep
> things fast.

mirrorlist server I put there doesn't hit the database ever. It's got
a private cache file updated hourly from a process run on app4. :-)

--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux

_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
 
Old 04-24-2008, 02:25 AM
Mike McGrath
 
Default app6 up

latency and throughput measure different things though, we'll have to test
multiple things.

-Mike

On Wed, 23 Apr 2008, Toshio Kuratomi wrote:

> Answering myself, ping times from app4 (phx-Arizona), app5.vpn
> (tummy-Colorado), and app6.vpn(telia-Germany) to db2(phx-Arizona)
>
> [toshio@app4 ~]$ ping db2
> PING db2.fedora.phx.redhat.com (10.8.34.120) 56(84) bytes of data.
> 64 bytes from 10.8.34.120: icmp_seq=1 ttl=64 time=0.249 ms
> 64 bytes from 10.8.34.120: icmp_seq=2 ttl=64 time=0.285 ms
> 64 bytes from 10.8.34.120: icmp_seq=3 ttl=64 time=0.764 ms
> 64 bytes from 10.8.34.120: icmp_seq=4 ttl=64 time=0.280 ms
>
> [toshio@app5 ~]$ ping db2
> PING db2.vpn.fedoraproject.org (192.168.1.19) 56(84) bytes of data.
> 64 bytes from 192.168.1.19: icmp_seq=1 ttl=64 time=43.7 ms
> 64 bytes from 192.168.1.19: icmp_seq=2 ttl=64 time=42.9 ms
> 64 bytes from 192.168.1.19: icmp_seq=3 ttl=64 time=42.9 ms
> 64 bytes from 192.168.1.19: icmp_seq=4 ttl=64 time=42.9 ms
>
> [toshio@app6 ~]$ ping db2
> PING db2.vpn.fedoraproject.org (192.168.1.19) 56(84) bytes of data.
> 64 bytes from 192.168.1.19: icmp_seq=1 ttl=64 time=196 ms
> 64 bytes from 192.168.1.19: icmp_seq=2 ttl=64 time=181 ms
> 64 bytes from 192.168.1.19: icmp_seq=3 ttl=64 time=184 ms
> 64 bytes from 192.168.1.19: icmp_seq=4 ttl=64 time=186 ms
>
> So each request from an app server in phx to the database or to another app
> will be 200x faster to set up than from an app server at tummy and nearly
> 1000x faster to set up than telia. If we deploy apps at telia it will be
> essential to minimize the number of requests if we want to keep things fast.
>
> -Toshio
>
>

_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
 

Thread Tools




All times are GMT. The time now is 02:50 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org