comment on

In addition to what afoken said, try adding indices to your table.

CREATE INDEX CT_Media_Relations_ix_SupplierID
          ON CT_Media_Relations   (SupplierID);

CREATE INDEX CT_Media_Relations_ix_SupplierPID
          ON CT_Media_Relations   (SupplierPID);

-- etc
[download]

Indices will somewhat slow down write queries (INSERT, etc) but can have a huge improvement on read queries (SELECT, etc).

Any primary keys will already be indexed, but any other columns containing numbers, dates, and short strings which you frequently filter, sort, or group by should probably be indexed.

Hire me at Toby Ink Ltd or Join my OnlyFans

In reply to Re: performance with mysql / file-caching / hash reference on demand by tobyink
in thread performance with mysql / file-caching / hash reference on demand by derion

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks