[
http://opencast.jira.com/browse/MH-8854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30823#comment-30823
]
Stephen Marquard commented on MH-8854:
--------------------------------------
For this particular query, it is marginally better to create a single compound
index:
create index user_action_session_type_i on user_action(session_id, type);
Does make any wonder if the query itself is optimal though - e.g. should it be
limited by mediapackage?
Also it seems user_action should at least have separate type and data fields,
as type contains items like
| SET_VOLUME-0.375 |
| SET_VOLUME-0.5 |
| SET_VOLUME-0.625 |
| SET_VOLUME-0.75 |
and oddly
| SEARCH-al |
| SEARCH-alg |
| SEARCH-algo |
| SEARCH-algor |
| SEARCH-algori |
| SEARCH-algorit |
and
| RESIZE_TO-906x1185 |
| RESIZE_TO-906x1200 |
| RESIZE_TO-907x1200 |
| RESIZE_TO-908x1200 |
| RESIZE_TO-911x1200 |
| RESIZE_TO-911x623 |
| RESIZE_TO-912x1200 |
| RESIZE_TO-913x1200 |
| RESIZE_TO-914x1200 |
| RESIZE_TO-914x613 |
| RESIZE_TO-914x625 |
none of which will help db performance (e.g. it would be inefficient to query
for RESIZE_TO_*).
> user_action table definition leads to ineficient queries on mysql
> -----------------------------------------------------------------
>
> Key: MH-8854
> URL: http://opencast.jira.com/browse/MH-8854
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Architecture & Services
> Affects Versions: 1.2
> Reporter: David Horwitz
> Assignee: Ruediger Rolf
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
