×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Holger,
Am 18.08.2022 um 11:39 schrieb Holger Scherer <hs@xxxxxxx>:
Good databases do this on their own. What database are we discussing about?
What exactly is "this"? As far as I've understood how databases work, records might need to be locked, no matter if the data comes from a database-internal cache or being refreshed through a true query execution. I can't remember if contention was accelerated by the the tables being of type MyISAM (no row locking, always global table locks) for some reason, or if I could successfully migrate them to the InnoDB backend (allowing finer-grained row-level locks). (MySQL/MyISAM was initially developed and praised for its efficiency with short-lived connections — from e. g. PHP — and quick responses for SELECTs.)
My experience stems from a former employer with MySQL on Linux using PHP for a home-grown ticketing system tracking customer requests for changes and incidents. I wasn't the programmer, but the system administrator being faced with frequent "database is slow, do something" requests.
:wq! PoC
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
