I’ve asked this in the channel but could use more than one sentence:
what is the current status of using sqlite as the db for RT? Where I
work at they like sqlite a lot but from what I have read so far (could
be outdated docs), it is not ready for prime time just yet. So, has
anyone used it? If so, what are your experiences?
I’ve asked this in the channel but could use more than one sentence:
what is the current status of using sqlite as the db for RT? Where I
work at they like sqlite a lot but from what I have read so far (could
be outdated docs), it is not ready for prime time just yet. So, has
anyone used it? If so, what are your experiences?
SQLite is primarily intended for development and testing environments.
It’s not well-suited to a multi-user production environement for RT.
Best,
Jesse
SQLite is primarily intended for development and testing environments.
It’s not well-suited to a multi-user production environement for RT.
Actually, I think SQLite’s mission is to provide a lightweight database for
individual use applications. It’s used by a lot of such things such as Apple
Mail, Safari, Firefox, Google Gears, and the Skype client. But it certainly
isn’t robust enough for the enterprise side of things. Google Gears on SQLite
sure, but Google itself? Skype client yes, but Skype servers? Not gonna happen.
– ============================
Tom Lahti
BIT Statement LLC
(425)251-0833 x 117
http://www.bitstatement.net/
– ============================
SQLite is primarily intended for development and testing environments.
It’s not well-suited to a multi-user production environement for RT.Actually, I think SQLite’s mission is to provide a lightweight database for
individual use applications. It’s used by a lot of such things such as Apple
Mail, Safari, Firefox, Google Gears, and the Skype client. But it certainly
isn’t robust enough for the enterprise side of things. Google Gears on SQLite
sure, but Google itself? Skype client yes, but Skype servers? Not gonna happen.
RT is very slow when using sqlite. I’ve installed rt3.6 from debian with
sqlite and after about 300 tickets, I was forced to go through a painful
process of migrating data to mysql. With mysql rt is about 10 times faster.
mk
SQLite is primarily intended for development and testing environments.
It’s not well-suited to a multi-user production environement for RT.Actually, I think SQLite’s mission is to provide a lightweight database for
individual use applications. It’s used by a lot of such things such as Apple
Mail, Safari, Firefox, Google Gears, and the Skype client. But it certainly
isn’t robust enough for the enterprise side of things. Google Gears on SQLite
sure, but Google itself? Skype client yes, but Skype servers? Not gonna happen.
Sorry. What I meant to say is “RT’s SQLite support” - I love SQLite
for all sorts of applications. multi-user apps with SQLite are totally
doable – you just need to be careful with write concurrency 
Sorry. What I meant to say is “RT’s SQLite support” - I love SQLite
for all sorts of applications. multi-user apps with SQLite are totally
doable – you just need to be careful with write concurrency
If you leave synchronous writes on, you’re limited on transaction speed. A
commit takes at least two full drive rotations, so for a 7200rpm drive you can
only do 60 transactions per second. Not terribly scalable 
– ============================
Tom Lahti
BIT Statement LLC
(425)251-0833 x 117
http://www.bitstatement.net/
– ============================
Tom Lahti wrote:
Sorry. What I meant to say is “RT’s SQLite support” - I love SQLite
for all sorts of applications. multi-user apps with SQLite are totally
doable – you just need to be careful with write concurrencyIf you leave synchronous writes on, you’re limited on transaction speed. A
commit takes at least two full drive rotations, so for a 7200rpm drive you can
only do 60 transactions per second. Not terribly scalable
I am in a small shop (12 people tops). If we end up having 60 tickets
per minute, I would be happily amazed and glad to upgrade to mysql or
something else.
Tom Lahti wrote:
Sorry. What I meant to say is “RT’s SQLite support” - I love SQLite
for all sorts of applications. multi-user apps with SQLite are totally
doable – you just need to be careful with write concurrencyIf you leave synchronous writes on, you’re limited on transaction speed. A
commit takes at least two full drive rotations, so for a 7200rpm drive you can
only do 60 transactions per second. Not terribly scalableI am in a small shop (12 people tops). If we end up having 60 tickets
per minute, I would be happily amazed and glad to upgrade to mysql or
something else.
No, really, don’t do that. We haven’t tested RT 3.x on SQLite in a
production environment. That’s not a supported configuration. I have no
idea how badly it might hurt you.
Jesse Vincent (RT’s Architect)
Tom Lahti wrote:
Sorry. What I meant to say is “RT’s SQLite support” - I love SQLite
for all sorts of applications. multi-user apps with SQLite are totally
doable – you just need to be careful with write concurrencyIf you leave synchronous writes on, you’re limited on transaction speed. A
commit takes at least two full drive rotations, so for a 7200rpm drive you can
only do 60 transactions per second. Not terribly scalableI am in a small shop (12 people tops). If we end up having 60 ticketsper minute, I would be happily amazed and glad to upgrade to mysql or
something else.No, really, don’t do that. We haven’t tested RT 3.x on SQLite in a
production environment. That’s not a supported configuration. I have no
idea how badly it might hurt you.
with 300 tickets on a machine running on xen, it’s been unusable. took about
15 seconds just to show a ticket. the problem was disk io. underlying disk
space was a hardware raid1 on SAS disks. now with mysql, it takes about 2
seconds to show a ticket.
mk
with 300 tickets on a machine running on xen, it’s been unusable. took about
15 seconds just to show a ticket. the problem was disk io. underlying disk
space was a hardware raid1 on SAS disks. now with mysql, it takes about 2
seconds to show a ticket.
That still sounds really high. Do you perhaps have xen snapshots on or
something?
Is it swap drive io??
I’ve had this happen when RT tries to process a large attachment… see if the mailbox it’s pulling from has an email with a large attachment in it.
Mike Johnson
Datatel Programmer/Analyst
Northern Ontario School of Medicine
955 Oliver Road
Thunder Bay, ON P7B 5E1
Phone: 807.766.7331
Email: mike.johnson@normed.ca
Technology assistance: email nosmhelpdesk@normed.ca
Technology Emergency Contact (TEC) Mon-Fri, 8am to 5pm excluding stat holidays:
Off campus toll free 1-800-461-8777, option 8, or locally either
(705)-662-7120 or (807)-766-7500
Jesse Vincent jesse@bestpractical.com 23/09/2009 11:24 am >>>
with 300 tickets on a machine running on xen, it’s been unusable. took about
15 seconds just to show a ticket. the problem was disk io. underlying disk
space was a hardware raid1 on SAS disks. now with mysql, it takes about 2
seconds to show a ticket.
That still sounds really high. Do you perhaps have xen snapshots on or
something?
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com ( http://wiki.bestpractical.com/ )
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com ( http://rtbook.bestpractical.com/ )