Out of your 4 gigabyte of memory, you allocate 2G to the innodb pool.
Assuming you're using mostly innoDB, that's good. Say there's also about
300M allocated to the OS - assuming a dedicated server; that leaves about
1.7G for non-InnoDB operations.
You have configured your server for 500
Good day all
I am hoping that someone can perhaps help me with some resources
or info.
I need to go to a meeting in the next hour and was requested this
morning to research possible load balancing options for MySQL database.
What is currently running is a website (balanced
http://www.mysql.com/products/
So the free version is going to include only MyISAM? And you won't be
able to connect using MySQL Workbench (and presumably apps like MySQL
Query Browser)? Otherwise you have to shell out $2k? Wow. I think
it might be time to start seriously looking at
If your sites are busy with *writes*, you're kind of stuck. Replication
means that every write that happens on one side, also MUST happen on the
other side, so you win nothing. Well, you win a little delay on half of your
writes, which is, to most people, really a downside, not an upside.
Your
You may want to read that again, but with your glasses on :-)
Subscription means roughly commercial support. The (1) subscript means
Features only available in Commercial Editions, and is noted *only* for
Workbench SE, Enterprise Monitor, Enterprise Backup and Cluster Manager.
I will join you in
Thank you for the quick response
just to answer one of the things here, the load is mostly reads as
writes only happen in batches every so often.
When I am saying reads I am talking of up to 2000-5000 concurrently at
any given time during high load.
-Original Message-
From:
And here's the answer to that, too:
MySQL Workbench is available in two editions, the GPL “Community Edition”
and the commercial “Standard Edition”.
The MySQL Workbench Community Edition can be downloaded from the MySQL
Developer Site http://dev.mysql.com/downloads/workbench/.
MySQL Workbench
Hi!
Christoph Boget wrote:
http://www.mysql.com/products/
So the free version is going to include only MyISAM? [[...]]
Totally wrong.
Classic is the name of a configuration for commercial customers
(typically: for use in embedded applications) that refers to the
pre-InnoDB times.
It is
On Thu, Nov 4, 2010 at 5:13 AM, Christoph Boget
christoph.bo...@gmail.com wrote:
I think
it might be time to start seriously looking at Postgres...
Even though all the info you provided is extremely
exaggerated...switching all my databases to PostgreSQL has been the
best thing I've done in
On the other hand, they've only with this release managed to implement live
log shipping, among other things :-)
Both are bound to have pros and cons.
On Thu, Nov 4, 2010 at 2:17 PM, Carlos Mennens carlosw...@gmail.com wrote:
On Thu, Nov 4, 2010 at 5:13 AM, Christoph Boget
Hi,
I found that mysql server stops and starts automatically from time to
time. I am not sure what is causing this.
Log:
-
100923 18:51:29 mysqld started
100923 18:51:29 InnoDB: Started; log sequence number 0 43655
100923 18:51:30 [Note] /usr/libexec/mysqld: ready for connections.
Version:
I don't see any thing written dmesg and message releated to this.
Does this have to do something with performance tuning? or can be
tuned to make better.
my.cnf looks:
[mysqld]
key_buffer = 128M
sort_buffer = 1M
join_buffer = 1M
max_allowed_packet = 8M
max_heap_table_size = 16M
table_cache =
On Thu, 4 Nov 2010 08:07:02 -0300
Paul Halliday paul.halli...@gmail.com wrote:
SELECT COUNT(signature) AS count, MAX(timestamp) AS maxTime,
INET_NTOA(src_ip), src.cc, INET_NTOA(dst_ip), dst.cc FROM event LEFT
JOIN mappings AS src ON event.src_ip = src.ip LEFT JOIN mappings AS
dst ON
Presumably those records were absorbed into your 'group by' clause, since
there was an entry, from a later time, which had the same values for all the
group by fields.
--
Simcha Younger sim...@syounger.com
Geez, how obvious. I was thinking on a completely different plane. I
feel pretty
Hi,
I rebooted my RHEL and the segmentation fault is gone.
regards.
On Tue, Sep 28, 2010 at 1:58 PM, Sharath Babu Dodda sharath.do...@gmail.com
wrote:
Hi,
Any more solutions on this please.
Thanks,
Sharath.
On Mon, Sep 27, 2010 at 6:17 PM, Sharath Babu Dodda
sharath.do...@gmail.com
Classic scenario where MMM will be your best bet. Check out
http://mysql-mmm.org for more information. Setup two masters and 2 or
more slaves for full High Availability. It scales extremely well if
your application is read-heavy (which most applications are).
If you need help implementing this, I
CREATE TABLE `abc` (
`threadid` int(11) NOT NULL AUTO_INCREMENT COMMENT '主题id',
`thread_type_id` int(11) DEFAULT NULL COMMENT '主题类别表id',
`forumid` smallint(6) DEFAULT NULL COMMENT '主键id',
`title` varchar(250) DEFAULT NULL COMMENT '标题',
`lastpost` int(11) DEFAULT NULL COMMENT '最后回复时间',
17 matches
Mail list logo
