[Freeswitch-users] Storing CDR UUIDs in MySQL

Steven Ayre steveayre at gmail.com
Mon Feb 18 00:11:48 MSK 2013

Another possibility you haven't looked at is having a table of UUIDs with a
BIGINT auto_increment PK and using that as keys in other takes with a
foreign key relationship (whether defined or implied). That would give you
a smaller integer (hence faster select/insert/join/etc) that's still
guaranteed to be unique. Though the auto_increment INSERT could then become
a bottleneck (hint run a recent 5.5/5.6 MySQL version at the very least
since that bottleneck while still present was very much reduced).


On 17 February 2013 20:55, Cal Leeming [Simplicity Media Ltd] <
cal.leeming at simplicitymedialtd.co.uk> wrote:

> Hi all,
> Just spent a little while comparing the performance of heavy INSERT/SELECT
> performance against UUID fields in a MySQL database.
> Full performance breakdown and write up can be found here;
> http://blog.simplicitymedialtd.co.uk/?p=437
> So far, the best option seems to be storing the UUID as a BINARY(16) -
> anyone have any thoughts on this?
> Thanks
> Cal
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20130217/7dca34df/attachment.html 

Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users mailing list