Mailinglist Archive: opensuse (3232 mails)
| < Previous | Next > |
Re: [SLE] a long-time Suser compares kubuntu and Suse
- From: suse@xxxxxx
- Date: Mon, 21 Aug 2006 14:51:29 +0000 (UTC)
- Message-id: <44E9C868.6070507@xxxxxx>
Per Jessen wrote:
> suse@xxxxxx wrote:
>
>> "Installation" of what?
>
> Of an entire system.
The initial install has never been the problem.
>> How long does it take in 10.2 to add a new source, bring up the
>> software management, find the program you want, and install it?
>> (and no, the new repo can't be connected to you via lan)
>
> Sorry, that's all I use, so I can't say.
Well, that's where the problem has been.
>> I'm guessing that the connection speed to the repo is key.
>
> In 10.1 a lot of the lack of speed was due to Yast/Zmd/rug, not the
> access-speed to the source. I always install from local sources, and I
> guarantee 10.2 is a lot faster.
That may be the case, but when zen/rug decides to repeatedly download
the same large repodata files over and over, that's the problem we're
talking about! It's the massive delays every time you bring up software
management. It's the throttling of the machine every time you wake up
zmd. These are the issues.
Once it had things downloaded and parsed, actually installing things may
not have been the fastest, but it wasn't sitting there for an hour
looking like it had completely crashed.
I'm guessing that because it was first designed as a zenworks interface,
all design assumptions were that repo's were local or on the lan, since
that is the environment ZenWorks was designed for.
There's also the problem of random mirror redirection. I discovered
this when I tried pointing smart at the build system early on. You
might have a good connection to one mirror, but it will redirect you to
whatever mirror it feels like, no matter how crappy your connection to
it is.
Maybe this is why SuSE doesn't seem to get what we're screaming about?
They're all connected closely to their local repo, so they're not seeing
what we are and are assuming that the slowness you're talking about
above is what we've been complaining about. It isn't. Sure, the
slowness is less than optimal, but it isn't the hour-long crash
look-a-like those of us in the states trying to use repo's in Germany get.
If the problem was just the speed of install from a local repo, it could
be fixed by the "improvements" they've mentioned. But what we're seeing
over here is MUCH worse.
> suse@xxxxxx wrote:
>
>> "Installation" of what?
>
> Of an entire system.
The initial install has never been the problem.
>> How long does it take in 10.2 to add a new source, bring up the
>> software management, find the program you want, and install it?
>> (and no, the new repo can't be connected to you via lan)
>
> Sorry, that's all I use, so I can't say.
Well, that's where the problem has been.
>> I'm guessing that the connection speed to the repo is key.
>
> In 10.1 a lot of the lack of speed was due to Yast/Zmd/rug, not the
> access-speed to the source. I always install from local sources, and I
> guarantee 10.2 is a lot faster.
That may be the case, but when zen/rug decides to repeatedly download
the same large repodata files over and over, that's the problem we're
talking about! It's the massive delays every time you bring up software
management. It's the throttling of the machine every time you wake up
zmd. These are the issues.
Once it had things downloaded and parsed, actually installing things may
not have been the fastest, but it wasn't sitting there for an hour
looking like it had completely crashed.
I'm guessing that because it was first designed as a zenworks interface,
all design assumptions were that repo's were local or on the lan, since
that is the environment ZenWorks was designed for.
There's also the problem of random mirror redirection. I discovered
this when I tried pointing smart at the build system early on. You
might have a good connection to one mirror, but it will redirect you to
whatever mirror it feels like, no matter how crappy your connection to
it is.
Maybe this is why SuSE doesn't seem to get what we're screaming about?
They're all connected closely to their local repo, so they're not seeing
what we are and are assuming that the slowness you're talking about
above is what we've been complaining about. It isn't. Sure, the
slowness is less than optimal, but it isn't the hour-long crash
look-a-like those of us in the states trying to use repo's in Germany get.
If the problem was just the speed of install from a local repo, it could
be fixed by the "improvements" they've mentioned. But what we're seeing
over here is MUCH worse.
| < Previous | Next > |