Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Before you start, remember to have generic monitoring tools in place. Zabbix or Munin can tell you where the general resource bottlenecks are (e.g. memory, CPU, I/O), database-specific log-analysis tools like PgBadger can tell you what queries are slow, etc.</p> <p>I will answer indirectly, by available technology and time to implement:</p> <p>1) If you have many different metrics that you want to start logging as soon as possible, and can worry later about retrieving the data (for example, you don't know exactly what you want to measure, so you just want to dump everything you can), you could some NoSQL database like MongoDB or Redis.</p> <p>Later, you can play with the data. Not very efficient for retrieval.</p> <p>2) If you like agile approach, start small. Choose any backend (SQL, text files), and dump only some data, and later extend it with more columns depending on what first investigation shows you. Table design depends only on your app. For an MVC web application, it could be controller / action / user_id / total_pageload_time / memory_used. Then you can simply group by controller and see which parts are slow. SQLite works well for write-only data like this from my experience.</p> <p>3) If you need to micro-optimize, you should probably look for official an unofficial plugins or external tools for your server software (e.g. PgBadger for PostgreSQL, etc).</p> <p>Anyway, considering you "ideal attributes", I'd go with some kind of SQL server with small tables at first, adding tracked parameters incrementally instead of trying to come up with one perfect forever-lasting table design.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat are some good ways to store performance statistics in a database for querying later?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USanalytik_work
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload