Date: Thu, 12 Feb 2009 18:49:20 -0800 From: Xin LI <delphij@delphij.net> To: Karl Denninger <karl@denninger.net> Cc: freebsd-stable@freebsd.org Subject: Re: Upgrade from 32-bit to AMD-64? Message-ID: <4994DFB0.3060704@delphij.net> In-Reply-To: <4994DBC1.2000309@denninger.net> References: <4994CD7B.7040302@denninger.net> <4994D603.2060406@delphij.net> <4994D931.4060508@denninger.net> <4994DACC.1040801@delphij.net> <4994DBC1.2000309@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Karl Denninger wrote: [...] > I guess I need to schedule the 2-3 hours of downtime..... the reason for > this, by the way, is that I have a dbms app on there that is getting too > RAM hungry for its own good (its a Quadcore CPU) and I'm up against the > RAM limit for 32-bit code. The board will support more but 32-bit code > won't; ergo, the only way to get beyond this is to go to 64-bit. Oh wait! One thing you wanted to know is that, some database *can* have different on-disk format for 32-bit and 64-bit binaries. Be sure to have a dump handy. Last time I hit this on a MySQL "upgrade" between two servers, and I end up using its replication functionality. The operation took longer time than I expected at the beginning. My personal suggestion is that you do an experiment on another box (64-bit capable) to make sure that the data would work, this never hurts and avoids surprises (you do want 64-bit compile of your database application since you want to take full advantage of 64-bit OS); also, just like all upgrades, full backup is advised. Cheers, - -- Xin LI <delphij@delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmU37AACgkQi+vbBBjt66BzlwCfUuQuTY8rXnhE/T1K9BNIZ7bi j9sAoJiPJApQrX5Gwd4kfFWoiGfQs44g =0oRk -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4994DFB0.3060704>