DL Redden said:
> Wouldn't it be nice if the installer was smart enough to sniff out the
> machine info and suggest a reasonable list of configurations to choose
> from based on the machine size. That would be most useful for getting
> started right out of the box.

Although it's possible to write something that probed a box's config, it
would be a lot of very platform-specific maintenance. Maybe we could write
something on a GPL basis as a community with designated maintenance teams
for each supported platform ... ?

--
Bye now,
Obnoxio

"I'm astonished anyone pays real money for this crap."
-- Cosmo

--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.

Obnoxio The Clown schrieb:
> DL Redden said:
>> Wouldn't it be nice if the installer was smart enough to sniff out the
>> machine info and suggest a reasonable list of configurations to choose
>> from based on the machine size. That would be most useful for getting
>> started right out of the box.
>
> Although it's possible to write something that probed a box's config, it
> would be a lot of very platform-specific maintenance. Maybe we could write
> something on a GPL basis as a community with designated maintenance teams
> for each supported platform ... ?
>

First - I am not an expert is this things! Just a user.
Maybe the solution is, to offer a solution ready
to run with Knoppix or some such bootable Linux
or even packaged for vmware player.

At least the virtalizers expect that a user is able
to tell the player, how much memory and free disk
is available.

Both 'd be interesing for
tiny & old, laptop style, small server, medium server.
Tiny & old or laptop means that you have like 30-40 GB
free disk.
Server style today means: the cheaper the things the
bigger the disks, so one can expect upto 500GB of free disk space

I run a laptop with linux and the luxury of a 160 GB disk.
This thing also has a core 2 duo CPU and 2GB of RAM and
Gigabit Ethernet
-> successfully testing
with CPUVPS set to 8, and NETVPS also set to 8.
Load avg is approx at 85%, if stress testing with 500 users
on apache/tomcat/perl on a second machine using the laptop
as DB server and IDS V10UC3 as database SW
A comparably huge dual quadcore XEON blade is only 30% faster

dic_k
--
Richard Kofler
SOLID STATE EDV
Dienstleistungen GmbH
Vienna/Austria/Europe

Richard Kofler said:
> Obnoxio The Clown schrieb:
>> DL Redden said:
>>> Wouldn't it be nice if the installer was smart enough to sniff out the
>>> machine info and suggest a reasonable list of configurations to choose
>>> from based on the machine size. That would be most useful for getting
>>> started right out of the box.
>>
>> Although it's possible to write something that probed a box's config, it
>> would be a lot of very platform-specific maintenance. Maybe we could
>> write
>> something on a GPL basis as a community with designated maintenance
>> teams
>> for each supported platform ... ?
>>
>
> First - I am not an expert is this things! Just a user.
> Maybe the solution is, to offer a solution ready
> to run with Knoppix or some such bootable Linux
> or even packaged for vmware player.

But are they supported platforms? Anyway, that's a different issue from
making it better out of the box for ALL users.

--
Bye now,
Obnoxio

"I'm astonished anyone pays real money for this crap."
-- Cosmo

--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.

Obnoxio The Clown schrieb:
> Richard Kofler said:
>> Obnoxio The Clown schrieb:
>>> DL Redden said:
>>>> Wouldn't it be nice if the installer was smart enough to sniff out the
>>>> machine info and suggest a reasonable list of configurations to choose
>>>> from based on the machine size. That would be most useful for getting
>>>> started right out of the box.
>>> Although it's possible to write something that probed a box's config, it
>>> would be a lot of very platform-specific maintenance. Maybe we could
>>> write
>>> something on a GPL basis as a community with designated maintenance
>>> teams
>>> for each supported platform ... ?
>>>
>> First - I am not an expert is this things! Just a user.
>> Maybe the solution is, to offer a solution ready
>> to run with Knoppix or some such bootable Linux
>> or even packaged for vmware player.
>
> But are they supported platforms? Anyway, that's a different issue from
> making it better out of the box for ALL users.
>
Although you are right, and I stand corrected as I did not
take into account the management point of view regarding
supported paltforms, as a matter of fact, I never had
as many technical problems on 'unsupported' distros than
I had them using RHEL or SuSE.

This may be my personal attitude, but if I take something
out of the box, I near to never run it on an enterprise
style Linux for the first couple of test.
One of the reasons is community support for kernel
relevant problems (like base address and shared library
load points etc.).
Maybe more important is the sad fact, that using an
enterprise distro means also going back approx 1 year
in time, because the long time to market of an
enterprise Linux distribution. Not many of the
community want to discuss solved problems over and
over again. Same starts to happen with Microsoft
as a platform: KB enties Vista vs prae-Vista is
like 10:1, therefore one can see where support
focus has moved to in only 9 weeks.


What tends to get more important for out of the box
install & testing in a corporate surrounding is to
avoid problems when running in a virtual machine, be it
Sol 10 zone or via XEN or parallels or vmware.
Many corporate customers are expected to have
testmachines on virtual environments only at the end of
this year.


On the documentation side of a new wrap up to
make IDS more ready to use right out of the box,
maybe we need a new manual, titled: how to make
your IDS admin free.
This booklet might be in shortcut form, like
O'Reilly does is, and brings together in one place
the things many of us DBAs do in the first hrs after
an installation. To name a few:
- separate & size physical log and logical
log into their own dbspaces
- create a dbspace for the CREATE DATABASE .. IN ...
to have system catalog in its own dbspace
- create temp dbspaces with and without 'T'-flag
and list them in $ONCONFIG
and so on.

All this IS actually documented quite well and
there are also script templates around on the
IIUG SW repository, but as we can see in c.d.i.
maybe this information needs a place where you
find it at a glance, even if you are new to IDS
and its documentation.

dic_k

--
Richard Kofler
SOLID STATE EDV
Dienstleistungen GmbH
Vienna/Austria/Europe

If the assumption is to install on Linux, then one could simply walk through
the boot up messages, such as what dmesg puts out, parse CPU information, or
also parse /proc/cpuinfo or /proc/meminfo, etc. These information sources are
relatively easy to find on Linux, however, it doesn't address other unix-type
platforms, or Windows.

Might want a combination of a recommended choice based on your system or choose from a list.

-t-

Obnoxio The Clown wrote:
> DL Redden said:
>> Wouldn't it be nice if the installer was smart enough to sniff out the
>> machine info and suggest a reasonable list of configurations to choose
>> from based on the machine size. That would be most useful for getting
>> started right out of the box.
>
> Although it's possible to write something that probed a box's config, it
> would be a lot of very platform-specific maintenance. Maybe we could write
> something on a GPL basis as a community with designated maintenance teams
> for each supported platform ... ?
>

--
*
* http://www.youtube.com/watch?v=rVS3k...elated&search=
*

Tool said:
> If the assumption is to install on Linux, then one could simply walk
> through
> the boot up messages, such as what dmesg puts out, parse CPU information,
> or
> also parse /proc/cpuinfo or /proc/meminfo, etc. These information sources
> are
> relatively easy to find on Linux, however, it doesn't address other
> unix-type
> platforms, or Windows.

Yes, it would be fairly easy to do with Linux, probably also easy but
different with (each different flavour of) Unix and possibly even easy but
different again with Windoze.

That's why, as a first approximation, I'd suggest a handful of half-decent
options, it's easier than trying to suss every possible platform
accurately.

> Might want a combination of a recommended choice based on your system or
> choose from a list.
>
> -t-
>
> Obnoxio The Clown wrote:
>> DL Redden said:
>>> Wouldn't it be nice if the installer was smart enough to sniff out the
>>> machine info and suggest a reasonable list of configurations to choose
>>> from based on the machine size. That would be most useful for getting
>>> started right out of the box.
>>
>> Although it's possible to write something that probed a box's config, it
>> would be a lot of very platform-specific maintenance. Maybe we could
>> write
>> something on a GPL basis as a community with designated maintenance
>> teams
>> for each supported platform ... ?
>>
>
> --
> *
> * http://www.youtube.com/watch?v=rVS3k...elated&search=
> *
>
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
> --
> This message has been scanned for viruses and
> dangerous content by OpenProtect(http://www.openprotect.com), and is
> believed to be clean.
>


--
Bye now,
Obnoxio

"I'm astonished anyone pays real money for this crap."
-- Cosmo

--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.

Obnoxio The Clown wrote:
> Tool said:
>> If the assumption is to install on Linux, then one could simply walk
>> through
>> the boot up messages, such as what dmesg puts out, parse CPU information,
>> or
>> also parse /proc/cpuinfo or /proc/meminfo, etc. These information sources
>> are
>> relatively easy to find on Linux, however, it doesn't address other
>> unix-type
>> platforms, or Windows.
>
> Yes, it would be fairly easy to do with Linux, probably also easy but
> different with (each different flavour of) Unix and possibly even easy but
> different again with Windoze.
>
> That's why, as a first approximation, I'd suggest a handful of half-decent
> options, it's easier than trying to suss every possible platform
> accurately.
>

True true.

I would prefer selecting from a list of configurations rather than seeing
the installation go through a lot of extra work trying to guesstimate what
would be best. Guessing would involve a lot of wheel spinning, rather than
simply allowing the user to pick from some choices, which have to be done
by a human anyway.

-t-

Obnoxio The Clown wrote:
> Tool said:
>> If the assumption is to install on Linux, then one could simply walk
>> through
>> the boot up messages, such as what dmesg puts out, parse CPU information,
>> or
>> also parse /proc/cpuinfo or /proc/meminfo, etc. These information sources
>> are
>> relatively easy to find on Linux, however, it doesn't address other
>> unix-type
>> platforms, or Windows.
>
> Yes, it would be fairly easy to do with Linux, probably also easy but
> different with (each different flavour of) Unix and possibly even easy but
> different again with Windoze.
>
> That's why, as a first approximation, I'd suggest a handful of half-decent
> options, it's easier than trying to suss every possible platform
> accurately.
>
>> Might want a combination of a recommended choice based on your system or
>> choose from a list.
>>
>> -t-
>>
>> Obnoxio The Clown wrote:
>>> DL Redden said:
>>>> Wouldn't it be nice if the installer was smart enough to sniff out the
>>>> machine info and suggest a reasonable list of configurations to choose
>>>> from based on the machine size. That would be most useful for getting
>>>> started right out of the box.
>>> Although it's possible to write something that probed a box's config, it
>>> would be a lot of very platform-specific maintenance. Maybe we could
>>> write
>>> something on a GPL basis as a community with designated maintenance
>>> teams
>>> for each supported platform ... ?
>>>
>> --
>> *
>> * http://www.youtube.com/watch?v=rVS3k...elated&search=
>> *
>>
>> _______________________________________________
>> Informix-list mailing list
>> Informix-list@iiug.org
>> http://www.iiug.org/mailman/listinfo/informix-list
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by OpenProtect(http://www.openprotect.com), and is
>> believed to be clean.
>>
>
>
Still leaves many questions which need some sort of "deduced" setting :

RESIDENCY? All Partial None
Kernel AIO? Yes / No
Affinity? Yes / No / How many?
Different Page Size dbspaces?
Read Ahead?
[L]TAPEDEV ... backups anyone? onbar?
Enterprise Replication?
HDR?
Fragmentation?

Having said that, I have scripts which generate "N" instances which
could easily be adapted to include a "how big?" sort of set of
questions, which include ER configuration, multiple temp dbspaces,
environment setups yada yada yada.

XPS has a "small / medium / large" sort of setting.

One can get a fairly decent instance running in under 256 Mb.

Still, I agree that it would be nice

Oh, and turn OFF dynamic logs - or at least down to 1 - oh that won't
work either

I think it may be easier just to have 3 $ONCONFIGS, small / medium / large.

Download it and install it

Paul Watson
Tel: +44 1414161772 +1 913-400-2620
Mob: +44 7818003457 +1 913-636-2858
Web: www.oninit.com

Failure is not as frightening as regret.

Attend IDUG 2007 San Jose, North America
May 6-10, 2007
Visit http://www.iiug.org/conf for more information.




> -----Original Message-----
> From: Obnoxio The Clown [mailtobnoxio@serendipita.com]
> Posted At: 17 March 2007 06:54
> Posted To: comp.databases.informix
> Conversation: Out of Box Experience for Cheetah.
> Subject: Re: Out of Box Experience for Cheetah.
>
>
>
> Richard Kofler said:
> > Obnoxio The Clown schrieb:
> >> DL Redden said:
> >>> Wouldn't it be nice if the installer was smart enough to
> sniff out
> >>> the machine info and suggest a reasonable list of
> configurations to
> >>> choose from based on the machine size. That would be most
> useful for
> >>> getting started right out of the box.
> >>
> >> Although it's possible to write something that probed a
> box's config,
> >> it would be a lot of very platform-specific maintenance. Maybe we
> >> could write something on a GPL basis as a community with
> designated
> >> maintenance teams for each supported platform ... ?
> >>
> >
> > First - I am not an expert is this things! Just a user.
> > Maybe the solution is, to offer a solution ready to run
> with Knoppix
> > or some such bootable Linux or even packaged for vmware player.
>
> But are they supported platforms? Anyway, that's a different
> issue from making it better out of the box for ALL users.
>
> --
> Bye now,
> Obnoxio
>
> "I'm astonished anyone pays real money for this crap."
> -- Cosmo
>
> --
> This message has been scanned for viruses and dangerous
> content by OpenProtect(http://www.openprotect.com), and is
> believed to be clean.
>