Sulu CMS’ Post

What attributes should logs contain? Anything and everything. Oh thanks John. Top quality advice. Thanks. Sheesh. No really - anything and everything! Any attribute that you think might be mildly interesting... log it! I can't tell you how many times that "just in case" feeling has saved my a** with a bug. My heuristic - if the attribute is anything that's mildly interesting to be now, it'll be useful when it's needed. The things I include in my logs: * HTTP request attributes * Domain object attributes * IDs of everything - builds, traces, domain objects etc * User attributes - ID, anonymous ID, no PII * Technology attributes - redis cluster name, database instance name, job id etc . The more context you have around events the quicker you can diagnose them. Any more questions? Leave them in the comments.

In #MariaDB, the concept of #PAGEIOLATCH waits specifically doesn't exist as it is a term from Microsoft #SQLServer, where it indicates that a query is waiting for a page to be read from or written to disk. However, similar disk I/O bottlenecks can occur in MariaDB, and their analysis requires focusing on MariaDB's storage engine mechanisms (e.g., #InnoDB). @minervadb #sql https://zurl.co/H6T9

In #MariaDB, the concept of #PAGEIOLATCH waits specifically doesn't exist as it is a term from Microsoft #SQLServer, where it indicates that a query is waiting for a page to be read from or written to disk. However, similar disk I/O bottlenecks can occur in MariaDB, and their analysis requires focusing on MariaDB's storage engine mechanisms (e.g., #InnoDB). @minervadb #sql https://zurl.co/H6T9

In #MariaDB, the concept of #PAGEIOLATCH waits specifically doesn't exist as it is a term from Microsoft #SQLServer, where it indicates that a query is waiting for a page to be read from or written to disk. However, similar disk I/O bottlenecks can occur in MariaDB, and their analysis requires focusing on MariaDB's storage engine mechanisms (e.g., #InnoDB). @minervadb #sql https://zurl.co/H6T9

In #MariaDB, the concept of #PAGEIOLATCH waits specifically doesn't exist as it is a term from Microsoft #SQLServer, where it indicates that a query is waiting for a page to be read from or written to disk. However, similar disk I/O bottlenecks can occur in MariaDB, and their analysis requires focusing on MariaDB's storage engine mechanisms (e.g., #InnoDB). @minervadb #sql https://zurl.co/H6T9

8 Common SQL Slow Query Statements and How to Optimize Them

Yesterday, We encountered an issue for a website of one of our clients slowing down. Discovered it was due to many sessions being created in the sessions table which makes the query getting slower and slower. There was a spike of traffic on the website. Immediately, We switched to memcached to store the sessions instead of MySQL. Memcached is a key-value store with a high performance because it connects directly with the RAM unlike MYSQL. However, since the RAM is volatile, Memcached is also not persistent for data storage and cannot be used to store long term data. If you're looking to store quickly and fast but not much, Memcached is a better alternative to MYSQL. #InnovativeSoftwareDeveloper #optimization #software #SoftwareDevelopment

[DEV PREVIEW] We're introducing support for more complex authentication scenarios via our upcoming Custom Authentication Headers & Credentials Generation Settings functionality. The scenario: You have an internal graph database with custom authentication requirements that rely on temporary credentials or authorization headers generated via an external authentication process, for instance via the use of Google Identity Aware Proxy The solution: You can now configure a custom credentials process command on your database connection in G.V() to trigger the authentication flow on behalf of the user and include the credentials as part of the requests made from G.V() to your database. G.V() simply requires you to put together a small script that executes your authentication flow and returns the relevant credentials/headers in a lightweight JSON format for our software to support the complex authentication needs of your database. We'll be releasing this new feature in early July. Want the best developer experience using your Apache TinkerPop graph database? Get started with a free trial of G.V() at https://gdotv.com! #graphdb

This article explains what, why, and how to use Transact-SQL snapshot backups.

It is easy to protect PL/SQL from leaking your algorithms and code. - https://lnkd.in/eppqxvjw #plsql #protect #securecode