CFTopper.com

Tip: Change the Railo port to port 80

We are really getting into Railo these days and enjoying it's blazing speed.
Here's a quick Railo tip..

To change the default railo server port from the current default of 8600 to port 80:

Open the C:\Program Files\Railo\conf\resin.conf file.
(You can use the free Notepad++ for this if you don't have another suitable editor, windows notepad won't do.)
You'll find <http address="*" port="8600"/> around line 62
Change that to port 80 and restart the server.

Tags: Tips

Posted by Topper at 07:57PM Permalink

Comments [0] - Leave a comment

MySQL Optimisation Tip #2: Store counters in seperate tables

Store counters in seperate tables

A common scenario, you have a "pages" table and you want to store a hit counter in that table so you will know which pages are the most popular, you would have something like:

CREATE TABLE `pages` (
`pageId` int(10) unsigned NOT NULL auto_increment,
`pageName` varchar(255) NOT NULL,
`pageHTML` text NOT NULL,
`pageHitCounter` int(10) unsigned NOT NULL default '0',
PRIMARY KEY (`pageId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Now when you want to update the hit counter you will do something like:

UPDATES pages set pageHitCounter = pageHitCounter+1 WHERE pageId = 12

This is fine for normal database schemas... but if you are using the MySQL Query Cache feature (which you should), every time you execute the update you will invalidate the cache making the whole cache feature just about useless.

Instead what you can do is store the hitCounter for each page in a seperate table.

So add something like

CREATE TABLE `pageHitCounter` (
`pageId` int(10) unsigned NOT NULL auto_increment,
`pageHitCounter` int(10) unsigned NOT NULL default '0',
PRIMARY KEY (`pageId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

and update that instead. That was a fairly contrived example but you get the idea - be careful not to invalidate the cache.

Posted by Topper at 06:38PM Permalink

Comments [2] - Leave a comment

MySQL Optimisation Tip #1 - Turn on the query cache

The Query Cache

If your using MySQL in production you should turn on the query cache - this is off by default ( even if you have installed using the wizard and choosen "dedicated server" ).

The query cache basically remebers the results of your queries and saves them from being executed twice unnecessarily resulting in huge performance improvements.

Bare in mind that any inserts or updates will reset the parts of the query cache that relate to the affect tables. Luckily most applications read from the table much more often that they write data into them.

How to turn on the Query Cache

Open your my.ini (or my.cfg) file in notepad and set query_cache_type to 1. There are 3 settings for this: 0 (disable / off), 1 (enable / on) and 2 (on demand).
Tip: If you can't find this in your config file, so just add it in.
Now you need to tell MySQL how much memory space to use. For this, find (or add) the query_cache_size option and set it to something that makes sense. This is a global setting so all sites and applications on the server will share this. You could try 30MB to start with
query-cache-size = 20M
You will need to restart MySQL for the caching to begin.

How to know of the cache is being used

After restarting your server, execute the following SQL:

SHOW STATUS LIKE 'q%';

You will get something like:

Qcache_free_blocks    1613
Qcache_free_memory    202554688
Qcache_hits    679493
Qcache_inserts    207317
Qcache_lowmem_prunes    0
Qcache_not_cached    4532
Qcache_queries_in_cache    3488
Qcache_total_blocks    8788

The important two are Qcache_queries_in_cache and Qcache_not_cached.

Qcache_queries_in_cache is the total number og queries that are currently cached in memory.

Qcache_not_cached is the total number of queries that were executed where MySQL could not use a cached version.

References

Tags: MySQL | Tips

Posted by Topper at 12:59PM Permalink

Comments [1] - Leave a comment

ColdFusion Optimisation Tip #1 - Use StructKeyExists instead of isdefined

Use StructKeyExists instead of isdefined

Many of ye know this old nugget already so sorry if you know this already but StructKeyExists is much much much faster than isdefined.

As Simon Whaylay says:
"IsDefined() checks not just if a variable exists, but if it is also syntactically correct. This clearly has runtime implications. That is why, when dealing with structures you should avoid isDefined() in favour of structKeyExists()."

The Proof

TEST 1
IsDefined: #endTime#ms

TEST 2
StructKeyExists: #endTime#ms

The Result

IsDefined over 100000 loops: 337ms

StructKeyExists over 100000 loops: 36ms

References

http://www.simonwhatley.co.uk/isdefined-vs-structkeyexists
http://mkruger.cfwebtools.com/index.cfm?mode=alias&alias=isdefined%20vs%20structkeyexists
http://corfield.org/entry/isDefined_vs_structKeyExists

Posted by Topper at 12:57PM Permalink

Comments [1] - Leave a comment

Tip: Change the Railo port to port 80

MySQL Optimisation Tip #2: Store counters in seperate tables

Store counters in seperate tables

MySQL Optimisation Tip #1 - Turn on the query cache

The Query Cache

How to turn on the Query Cache

How to know of the cache is being used

References

ColdFusion Optimisation Tip #1 - Use StructKeyExists instead of isdefined

Use StructKeyExists instead of isdefined

The Proof

The Result

References

About Topper on ColdFusion

Twitter Updates

I'm speaking at CF-United Europe!

My ColdFusion Software

My Blogs

Digging

My Work - Just Finished

Archive

Tags