I agree and we are rewriting this application ourselves to accomidate these types of issues of making it faster faster faster.
But I would like to "patch what I have" at the same time. Call me greedy Thanks Donny Lairson President http://www.gunmuse.com 469 228 2183 -----Original Message----- From: sol beach [mailto:[EMAIL PROTECTED] Sent: Friday, November 26, 2004 11:25 AM To: [EMAIL PROTECTED] Subject: Re: Take a normal Table and Make it a Heap table When your only tool is a hammer, then all problems are views as nails. A shovel is a great tool for creating a hole in the ground, but only when the "right" end is contacts the ground. You seems to be using the wrong end of the computer. With computers, you can have it good, fast, or cheap. Pick any two (& pay the price in the third). I wish you luck in re-inventing the wheel & rolling your own custom SCABALBLE application. P.S. Scalability needs to be designed into the archituecture from the start. It rarely can be bolted together after the bottlenecks are encountered, because bottlenecks result from inappropriate original design decisions. On Fri, 26 Nov 2004 11:12:38 -0700, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I have to pull in 200 search rows and store them temporarily in a Table > called xmllinks This is so I can track the click on the one link of the 200 > I bring down. Nothing is permanently stored in this table > > This is just a normal table in a db right now but during peak traffic times > it bogs down the MySql. What do I have to do to move this one table into a > heap of ram. I didn't code this software so please give me a little detail > as to whether this is done at the software side or the MySql side. Of what > I need to edit to stick this up into ram and verify that its there. I do > want to verify its actually there somehow. > > Thanks > Donny Lairson > President > http://www.gunmuse.com > 469 228 2183 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
