| 1 |
meino.cramer@×××.de writes: |
| 2 |
|
| 3 |
> I think there is some misunderstanding: |
| 4 |
> |
| 5 |
> Before migration to 64bit: |
| 6 |
> |
| 7 |
> /dev/sda3 is mounted on / and contains the 32bit Gentoo |
| 8 |
> |
| 9 |
> /dev/sda10 is mounted on /home/mcc/migration and will contain the |
| 10 |
> stuff of the 64bit Gentoo |
| 11 |
> |
| 12 |
> After migration I will *not* mount /dev/sda10 on / but will clear all |
| 13 |
> stuff from /dev/sda3 and move the contents from /dev/sda10 to |
| 14 |
> /dev/sda3. |
| 15 |
> |
| 16 |
> Is still valid what you said under this premissions, Wonko? |
| 17 |
|
| 18 |
That's how I understood it, although I assumed the temproary 64bit install |
| 19 |
would be on a 2nd drive, thus you would copy it back once it seems to |
| 20 |
work. No, I see no problem with this. |
| 21 |
|
| 22 |
About performance: I'm not sure it will be even noticeable. Yes, most |
| 23 |
drives (but not all) are organized so the first partitions go to the |
| 24 |
outside, which is faster. With LVM, I used to create two volume groups on |
| 25 |
my drive, a group for swap and the system, and another one for data. But |
| 26 |
then I thought it's not worth the effort, and I lose some of the LVM |
| 27 |
benefits. Well, with everything encrypted I don't get full performance |
| 28 |
anyway, so my case might be a little different. |
| 29 |
|
| 30 |
But the performance increase is only true when reading lots of data. I'm |
| 31 |
not sure how big the role of this is in real life. Access time is not |
| 32 |
influenced, it will on average take half a turn of the drive till the |
| 33 |
heads can access the data, and to me it looks like typical stuff a linux |
| 34 |
system does is reading many not so large files, cluttered around in the |
| 35 |
file system. But that's my guess only. And I understand that you like to |
| 36 |
optimize stuff - I like to do this too. But sometimes I think that the |
| 37 |
potential benefit might not be so large, compared to the time I spend |
| 38 |
moving data around to the ideal place, or the time I would need to spend |
| 39 |
thinking about how to tune things. Or the time you need to fix a problem |
| 40 |
that you know was working in the old system, but this is gone now and you |
| 41 |
cannot have a quick look at it, or just boot into it. You lose the |
| 42 |
opportunity to start your old system in order to compare the times of your |
| 43 |
big renderings. And maybe at one point you need to create some true 32bit |
| 44 |
applications? Happened to me. So I just chroot into my old system and |
| 45 |
build there. |
| 46 |
|
| 47 |
Oh, and you mentioned databases. Yes, mysql stores itsa data in machine- |
| 48 |
depenent form. You will need to dump the data and re-import it in the new |
| 49 |
system. You will be happy to still have the 32bit system in such a case :) |
| 50 |
|
| 51 |
Wonko |
Archives