I've got a server with 24 gigs in it and it works just fine. About 3 with 8
gigs and a few with 2 gigs. All running 4.1.1. And all of them run without
any problems on Xeon's with Hyperthreading.
Donny
> -Original Message-
> From: Jigal van Hemert [mailto:[EMAIL PROTECTED]
> Sent: Tuesd
Michael,
Add this to you're my.cnf and then restart mysql. See if that solves your
problem.
open-files-limit=36864
Donny
> -Original Message-
> From: Michael Bacarella [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 08, 2004 4:52 PM
> To: [EMAIL PROTECTED]
> Subject: Re: "Can't create t
age-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Neil Gunton
> Sent: Monday, March 08, 2004 3:11 PM
> To: Donny Simonton
> Cc: [EMAIL PROTECTED]; 'MySQL'
> Subject: Re: ORDER BY RAND() performance
>
> Donny Simonton wrote:
> > One other
really remember how well it works. Actually, I just tried this on
a table with 43 million entries and it took 0.0004 seconds.
Just some ideas.
Donny
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 08, 2004 2:36 PM
> To: Donny Simo
ORDER BY RAND(), just sucks in my opinion. We have created our own internal
randomization system because pretty much everytime you use it will show up
in the slow query log, because of the using temporary, using filesort it
does. Splitting your data into a hundred tables will still make it "using
You should change it to something like this:
Select * from posts group by user_id order by username, timestamp DESC
That should give you the last post.
Donny
> -Original Message-
> From: Darran Kartaschew [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 07, 2004 9:42 PM
> To: [EMAIL PROT
I started using 4.1.0 in a production environment 2 weeks after it was
released. Then when 4.1.1 came out I started using it before it was even
posted on the mysql.com website. And I am sure I will do the same with
4.1.2. Is it stable? Yes. Are there bugs? Depends on what you are doing,
but m
ROTECTED]
> Sent: Sunday, February 29, 2004 6:46 PM
> To: Donny Simonton; 'karthik viswanathan'; [EMAIL PROTECTED]
> Subject: RE: optimizing a select statement over a database with >50
> million recs
>
> Here i
me_id =56) to use IN.
It has proven to be much faster for me. But that won't speed it up .3
seconds.
Donny
> -Original Message-
> From: karthik viswanathan [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 29, 2004 5:41 PM
> To: Donny Simonton; 'karthik viswanath
Can you send us a new explain on this version?
Donny
> -Original Message-
> From: karthik viswanathan [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 29, 2004 4:12 PM
> To: [EMAIL PROTECTED]
> Subject: Re: optimizing a select statement over a database with >50
> million recs
>
> here
I'm about to pull my hair out on this one so I thought I would see if
somebody could point me in the right direction.
I have a subquery that like like so.
SELECT *
FROM Word
INNER JOIN DomainWord
USING ( word )
INNER JOIN Domain
USING ( domain )
WHERE Domain.domain = ANY(
SELECT Domain.domain
Kevin,
As I mentioned earlier, set this in you're my.cnf and restart mysql. It has
helped me on many occasions.
open-files-limit=36864
Donny
> -Original Message-
> From: Kevin Marks [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 23, 2004 6:27 PM
> To: [EMAIL PROTECTED]
> Subject: Re
Set this in you're my.cnf and restart and see if that solves your problem.
open-files-limit=36864
*** Don't ask me what that number is, it's just a random number.
Donny
> -Original Message-
> From: Ken Menzel [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 23, 2004 10:20 AM
> To: Chr
market you are in might only be looking for C
programmers, so you become a C programmer.
Just my opinion.
Donny
> -Original Message-
> From: Walt [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 22, 2004 7:52 PM
> To: Donny Simonton; 'Rhino'; [EMAIL PROTECTED
As a manager of over 20 programmers, I would say from a web point of via PHP
would be your best bet. Everybody who graduates today can program in Java,
and if they don't have any other skills I don't even interview them. I
consider Java programmers to be the MCSE of a few years ago.
Donny
> -
Chris,
Another option is to use | instead of commas. Unless you have pipes in your
file. :)
Donny
> -Original Message-
> From: Dan Nelson [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 20, 2004 2:55 PM
> To: Chris Fossenier
> Cc: [EMAIL PROTECTED]
> Subject: Re: White Space
>
> In t
Brian,
I know that I have been using 4.1.0 and 4.1.1 and when compared to 4.0.x,
4.1.x is much faster for us. We have been pushing over 3000 queries per
second with 4.1.1 without any problems. Now we aren't using utf8, but I
don't think that would really be the problem.
Donny
> -Original Me
The biggest problem I see is that you are using a text field and you don't
have an index on it anyway. Maybe you should use a different field type and
index it. That should make it a little bit faster.
Donny
> -Original Message-
> From: Lancashire, Pete [mailto:[EMAIL PROTECTED]
> Sent:
I'm using apache 2, and I'm not having any problems with it at all. It's a
little weird trying to get it configured the first time, but other than that
it's not bad. We have found that it can push a little more bandwidth and
the load seems to be a little lower than 1.x. But then again we are run
SELECT * FROM `support_start` WHERE (NOW() - (60*7)) > TO_DAYS(date)
Not the most optimized way of doing it, but it would work. 60 seconds in a
minute and 7 minutes is the example.
Donny
> -Original Message-
> From: Scott Haneda [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 28, 2
Eve,
You can look at http://www.mysql.com/doc/en/Column_types.html
Or:
[NATIONAL] CHAR(M) [BINARY | ASCII | UNICODE]
A fixed-length string that is always right-padded with spaces to the
specified length when stored. The range of M is 0 to 255 characters (1 to
255 prior to MySQL Version 3.23). Tr
Chris,
We have found the same thing, the more indexes you add the longer it takes
to add another index. This is because at least from what I understand is
the index/MYI file is recreated when you add another index.
I don't know enough about INNODB but based on what I do know you would do
much bet
I figured out a little trick yesterday, I do not recommend it, but I did
work for me. I installed the rpm of MySQL-server, installed the client via
rpm, then when it came to the shared libraries. I went and downloaded the
binary build of MySQL then found the files I needed and put them in the
rig
I have a new box that I am trying to install 4.1.1 on, and whenever I try to
use rpm to install either MySQL-shared-4.1.1-0.i386.rpm or
MySQL-shared-compat-4.1.1-0.i386.rpm. I get the dreaded messages below:
[EMAIL PROTECTED] src]# rpm -i MySQL-shared-compat-4.1.1-0.i386.rpm
warning: MySQL-shared
101 - 124 of 124 matches
Mail list logo
