| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Comments:
<0> i worked in SanFran and LA
<0> Pleasanton
<1> You like Cali?
<0> while i lived in Berekely
<1> Yeah, I know the area.
<0> i love it
<1> Move back.
<0> berekely or Plesenton
<1> We need more tax payers.
<0> heh
<1> Either.
<0> not more than poor Canada
<1> heh
<0> i lived in Burbank in LA
<1> I live in Long Beach
<0> nice
<0> that near LA?
<1> Eh, it works.
<0> or in LA
<1> Surprised you don't know where it is...
<0> i know
<1> It's like, famous. heh
<0> i'm bad with names
<0> i knw
<0> i've heard of it lot's
<1> You know the 710?
<0> i might have even been there as a kid
<0> i remember my dad taking us to the Balbo Bay Club
<0> i still have a polo shirt from there
<1> No idea.
<0> no, don't know 719
<0> err, 710
<1> Freeway. heh.
<2> long beach kicks *** over LA
<1> Mapquest Long Beach :)
<0> yeah
<1> Don't be lazy!
<1> man long beach
<0> info LongBeach
<2> i'd retire there, once I earn enough
<1> zircu, You live in LB?
<2> no, i'm up in norther cal, in Davis
<0> man this is a nice room
<1> Nice?
<0> friendly people
<1> No, we're mean.
<0> yeah
<0> heh
<1> zircu, You want to retire to LB? WHY?
<0> i'll take it over #fedora
<2> to surf
<1> Just remember, M3, when you get kicked, you can rejoin. Not like we kickbanned you.
<1> zircu, That's Huntington Beach.
<1> HB
<1> Not LB.
<0> why would i get kicked?
<3> fun
<1> Because we're mean, and want entertainment.
<0> ooo k
<2> will, that is just a few miles away right?
<1> Eh... yeah
<1> I guess I always figured people "dreamed" for a retirement. Not stated their reality...
<2> when I was a younger i just remember LB and how warm the water is
<1> Ugh... Cali has no warm water.
<1> Well, not sure compared to NorCal
<0> come to Kish Island for warm green water
<1> Ok, dream about HB then.
<1> !google huntington beach
<4> huntington beach: http://www.ci.huntington-beach.ca.us/
<2> you can't go in the water without a wet suit here
<2> and enjoy it
<5> how do you speed up a query like "SELECT DISTINCT field FROM table;" when there are a lot of records in the table with the same value for "field" (there is an index on that field)
<1> oh
<6> i guess this question is not new, please give me a ref: how do i add a trigger "on truncate"?
<1> You guys are interrupting our offtopic conversations about Cali... :(
<2> lol
<6> :-(
<0> good idea, i've to get some sleep too
<0> nice meeting u guys
<0> later
<6> oelewapperke: normalize it?
<5> I suppose I could put the field in a different table
<5> but it would be a lot of code changes
<2> oelewapperke: iirc, the only way is to maintain a summary table, if your're data is not very unique the query will most likely scan the table to get the result
<5> it does use the index
<5> but it's still taking way too long
<2> oelewapperke: i ***ume you have done a 'EXPLAIN' on the query
<5> yes
<5> | 1 | SIMPLE | wapperMonitorValue | index | NULL | hosts | 31 | NULL | 2118028 | Using index |
<2> oelewapperke: even if you have an index, mysql does a cacluation on data uniquness, if you have 10000 records but 5 unique values, a table scan is going to happen instead of a index
<5> that ****s
<5> then I HAVE to get it out ?
<2> i would, it is one of the biggest bottlenecks you will run into expecially if this table is modified a lot, ***umuming myisam
<5> would changing the tabletype help ?
<2> for things like this I have found that keeping a summary table is much easier, but does require more code changes
<2> well, i dont think it will in this case, cause of the way the data is distrubuted
<7> hmm mysql should be able to get the list of distinct values from just looking at the index
<7> have you run optimize table?
<5> no
<7> maybe the index is just messed up due to alot of DML
<5> DML ?
<7> data manipulalation language
<7> update, delete, insert ..
<5> I wonder if using InnoDB will make it faster ...
<2> oelewapperke: what kind of table is this?
<7> dunno .. innodb and myisam certainly handle index caches differently
<5> zircu: it has measurements in it ... lots of them
<7> also .. instead of using a summary table
<2> oelewapperke: like, is this a logging table?
<7> if the query is run frequently enough
<5> zircu: yes
<7> and the data does not change that often
<7> then you might benefit from using the query cache
<5> the data changes quite often
<2> myisam is known to be best for just a logging table but then agin query against it is a different story
<7> oelewapperke: that would indicate that your index structure could become quite inefficient
<2> best for logging for the speed of inserts
<7> if you are willing to live on the edge you might consider mysql 5.1's partitioning
<5> what will happen in this scenario :
<5> lots lots lots of inserts
<5> (wait for a month or 2)
<2> i would love to use 5.1 partitioning
<5> delete everything older than a month
<5> will it kill performance long-term ?
<7> you probaly want to run an optimize table after the delete
<7> to get a cleaned up index structure
<5> could I pull apart that table in a view and insert into the view perhaps ?
<7> that will not help
<5> have a table with the (id, host, command) and just have the id column in my real table
<2> the one thing to watch out for is locking out people while you clean and optimise the data
<7> the problem is that a btree index can become inefficient
<5> if it scans the table I'm probably better off not doing indexing at all
<7> as you add data .. and this is not cleaned up automatically if you delete
<5> but can I pull the table apart with a view ?
<7> oelewapperke: if it always uses a table scan
<7> then yes you are just slowing down your DML with the index
<5> how would I verify that lsmith ?
<7> if the index structure is messed up?
<2> oelewapperke: there is a nice webinar about indexing on the mysql website
<7> oelewapperke: no .. views do not pull apart the data at all
<5> so you cannot insert into a view ?
<7> thats whats partitioning is for
<7> oelewapperke: yes you can insert into a view
<7> but think of a few as an hardcoded select
<7> the data still resides inside the originating table
<5> how could I do that ? have a relation between two tables, create a view with the relationship collapsed, and then insert into it (without specifying the value of the column that links the 2 tables)
<2> http://www.mysql.com/news-and-events/on-demand-webinars/coding-indexing-2006-03-01.php
<7> and whenever you are operating on the view .. it implicitly runs the select in some way or another (either by merging or by creating a temp table)
Return to
#mysql
or
Go to some related
logs:
ubuntu gkrellm-themes
#linux
means GM suse linux
ubuntu rt2600
#ubuntu
php5-mcrypt debian
#physics
#debian
stfucopter
#suse
|
|