# Suggestion for design

**URL:** <https://forums.percona.com/t/suggestion-for-design/14001>\
**Category:** Percona Distribution for MySQL\
**Created:** [January 19, 2022, 8:46pm UTC](https://forums.percona.com/t/suggestion-for-design/14001 "2022-01-19T20:46:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![farrokh](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/farrokh/32/5131_2.png) [@farrokh](https://forums.percona.com/u/farrokh)\
**Post date:** [January 19, 2022, 8:46pm UTC](https://forums.percona.com/t/suggestion-for-design/14001/1 "2022-01-19T20:46:28Z")

</div>

We are designing a new database (mysql likely) for a log view project , i.e. ingesting large amount of logs (from cpu chips test logs) into the database and massage the data and make it more useful, couple of extra needs is the new table columns may need to add from time to time and the logs keep comings and need to parse and load. What primary design and tools and scrips to do you suggest? THX

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [January 19, 2022, 9:12pm UTC](https://forums.percona.com/t/suggestion-for-design/14001/2 "2022-01-19T21:12:35Z")

</div>

Every application is unique, so you will end up writing your own scripts to ingest the data from your cpu test logs and format it into SQL for inserting into the database. For databases that are mostly writes, I would recommend you use Percona Server for MySQL and use the MyRocks storage engine which is optimized for write-intensive applications, such as storing logs.