Hi @rosendo.cardoso,
Building Your Model
If responsiveness is not an issue when building your model, it is likely that your graphics are already good enough.
You can easily test your whether your graphics are good enough for running your model. Try closing ALL windows in FlexSim, including tree views, process flows, 3d views, tool panels, quick properties - everything - so that you are left with the main button panel at the top and nothing else. Then run your model at max speed. Is the model run speed appreciably faster than with views open? If so, this suggests that more powerful graphics would be helpful. If not, then your simulation is CPU constrained, meaning it is fairly complex and requires a lot of computation.
Single Model Run
You computer has enough memory for a single model run, so the possible bottlenecks are graphics, CPU, or both. You can test graphics as described above. If the model speeds up with all views closed, then more powerful graphics may be helpful. If the model is still too slow, even with all views closed, then you need a more powerful CPU.
Experimenter
Running two experiment instances simultaneously is probably overwhelming your hardware resources and greatly degrading your performance. The memory requirements for your model are quite high. As described in the general system guidelines, you need to have enough memory for each simultaneous instance of your model run, plus more for overhead and other system/OS processes. For your current PC's 16GB RAM, and your 7.5GB+ model, you should probably constrain the number of simultaneous experimenter runs to 1. You can do so within the Experimenter interface, Advanced tab, Max Cores widget:

You may also want to look into different modeling approaches that are less memory intensive, though this is a completely separate question and highly dependent on the nature of your simulation.