| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Billy Holmes wrote: |
| 5 |
>> It would |
| 6 |
>> also require many more queries to execute |
| 7 |
> |
| 8 |
> That's a ~62% savings. You can use a medium INT to reference the |
| 9 |
> pathname, and then use inner joins in your queries. |
| 10 |
|
| 11 |
You should set up a sf.net project and then we could move discussion off |
| 12 |
this list... :) |
| 13 |
|
| 14 |
I think that splitting the path may be a good idea. Inner joins really |
| 15 |
do not add much of a penalty to your query as long as everything is |
| 16 |
indexed. |
| 17 |
|
| 18 |
However, I'm not convinced it makes a big difference. So, the DB is |
| 19 |
100MB - it isn't like you're sending that over a wire at all - you just |
| 20 |
need to store it on the DB server. Having 2 20MB tables instead of 1 |
| 21 |
100MB table isn't going to make a big difference in final performance. |
| 22 |
|
| 23 |
The main area to optimize size-wise is what gets sent over the wire - |
| 24 |
and that is just a list of packages/flags already indexed so that |
| 25 |
clients do not do needless work. That will be pretty small in any case. |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 28 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 29 |
|
| 30 |
iD8DBQFDYPkgg2bN8aFizRkRAhKtAJ0fiWZy6/GS0uaewIm9FgE/di/yxQCfYx1l |
| 31 |
e/wKtM59CdWtxvTx+3H/rcY= |
| 32 |
=hwBL |
| 33 |
-----END PGP SIGNATURE----- |
Archives