How to filter data obtained with practical measurements and simulations to be concisely put into a paper? I'm a PhD candidate in Computer Science and I'm working on my first paper that should be published in a peer-reviewed journal (until now, I published only papers in conferences).
My project is a FPGA memory module, which uses a specific approach (the main idea) to obtain better performance in terms of access philosophy and capacity.

Now, the mentioned idea is naturally the bulk of the paper, with the math, proofs, algorithms, etc. behind it. But, since the module was synthesized and tested, I feel obliged to address its obtained "measures".

The process generated quite a lot data which become even more after the simulations were done. So, I'm not sure what charts/tables are appropriate to analyze and publish in a paper? (e.g. input->output delay for a range of inputs; parameters like max clock, number of logic elements; perhaps even (parts) of the schema; etc.)

As this seems a bit specific, I would like to broaden the scope of the question. Namely, the general issue here is how to filter data which does not directly contribute to the understanding of the main idea, but is the result of a finished project and can be used to reinforce the researched concept with practical measurements and simulations. This obtained data is large, so I'm asking for guidelines what could be considered concise enough to put into a paper.
Read a couple of dozen papers that are similar in nature (that is, in terms of the method and how the research question is addresssed) to yours and are in your target journal. Look at how they've supplied the sort of detailed information you're talking about.

As a rule-of-thumb, put it all into supplementary information. And then follow the advice of your edit and peer-reviewers, if they advise moving things. If there are particular numbers that contribute to your main narrative, put those numbers in the body of the paper, too.