1 |
On Wednesday 25 June 2003 00.16, Brian Jackson wrote: |
2 |
> Totally agree. I have 5 Gentoo boxes at work (probably more soon), and it |
3 |
> takes a ridiculously long amount of time to do searches. One thing I would |
4 |
> suggest is to develop as an external tool, and once it matures, then shoot |
5 |
> for inclusion into portage. another suggestion would be for it to support |
6 |
> more than one type of db (sleepycat, postgres, mysql, gdbm for example). If |
7 |
|
8 |
Yes, it would be nice to make it that way. I guess something like client -> |
9 |
client-db-interface-layer -> db-of-choice. |
10 |
|
11 |
> you try to make some postgres zealot put mysql on just to query packages, |
12 |
> you are going to get some very unhappy words directed your way. I can try |
13 |
> to help also in my spare time. |
14 |
|
15 |
Well there are plenty of perl modules to handle client-db-interface-layer but |
16 |
I suspect they will all have different APIs for the client. My thoughts are |
17 |
get one system to work then build on that. So long as the design is modular, |
18 |
that should be too difficult for those interested. :) |
19 |
|
20 |
tony |
21 |
|
22 |
> |
23 |
> --Brian Jackson |
24 |
> |
25 |
> On Tuesday 24 June 2003 05:00 pm, Tony Clark wrote: |
26 |
> > I wanted to quickly find a package with emerge -s whatever. I noticed |
27 |
> > that it seemed to be taking a long time now for basic searches. A couple |
28 |
> > of random example are presented below. Now in my case on the machine in |
29 |
> > question, it is probably a bit slower than need be as /usr/portage is nfs |
30 |
> > mounted but neither the nfs server, this client are what would be called |
31 |
> > slow machines and I run 100baset ethernet. |
32 |
> > |
33 |
> > 12 months ago I thought the search times where acceptable, nowdays they |
34 |
> > are pushing it and with the number of packages going into portage sooner |
35 |
> > rather than later it is going to be unacceptal. I would also suggest a |
36 |
> > centralised server approach using something like mysql as apposed to |
37 |
> > localised databases based on berekley or something else. reason being |
38 |
> > that a number a ppl are running home lans and they are increasing in |
39 |
> > popularity and there is no need to store N machines worth of data. mysql |
40 |
> > comes to mind as it is a popular database as there is a good chance that |
41 |
> > for some other application it is already running on the network. I know |
42 |
> > in my case thats so. |
43 |
> > |
44 |
> > I know this has been discussed in the past but always put down for |
45 |
> > reasons I largely agreed with, but the number of packages and times have |
46 |
> > changed. I don't mind helping out with this with some perl etc. What I |
47 |
> > was thinking on for the initial implementation would be just to store the |
48 |
> > information required for searching. I don't see a need to store all |
49 |
> > dependcies etc so the installation process actually becomes database |
50 |
> > driven. In this case the queriey times are so short to the actually |
51 |
> > installation time, no noticable speed up will take place. |
52 |
> > |
53 |
> > The floor is open, let the flames begin :) |
54 |
> > |
55 |
> > tony |
56 |
> |
57 |
> <snipped times> |
58 |
|
59 |
-- |
60 |
Contract ASIC and FPGA design. |
61 |
Telephone +46 702 894 667 |
62 |
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x633E2623 |
63 |
|
64 |
|
65 |
|
66 |
-- |
67 |
gentoo-dev@g.o mailing list |