Flow 3d Hardware Requirements

[Othon Sdcd]

Beaware that more powerful and expensive computers may not solve simulation studies in a practical timeframe if best practices are not observed. To learn more about tools and techniques to improve your Simulation studies, we recommend attending a SOLIDWORKS Simulation training course on the topic. This will provide much greater performance improvements compared to an overly expensive workstation.

The following gives details on specific hardware components. However the entire system should be designed and assembled for optimal performance. Custom machines can be a cheaper option, however selecting components individually may not be compatible or have bottlenecks. Cooling and thermal management is also an important aspect. Purchasing a machine from a computer manufacturer ensures all components will work together correctly.

All hardware of a computer is important to consider, but the CPU is still the most important component in terms of the speed for running Simulation studies. The CPU Clock Speed should be the first item to consider. A number of Simulation processes can only utilize a single CPU core while solving. Therefore the CPU Clock Speed would be the bottleneck as the other cores will not be used during this time. Look for a CPU speed of 4GHz or more.

We cannot expect the CPU to have 100% usage all the time. Larger studies may see better utilization of cores, however Microsoft Windows ultimately manages the CPU usage for each program based on requirements.

SOLIDWORKS Simulation and Flow Simulation creates a large amount of data. All of this data is been written to storage drives while the study is running. Having a high-performance CPU does not define how fast the calculated information is being saved. Therefore storage drives are a key performance aspect of a system.

Use an SSD drive with a read/write of at least 500MB/s if possible. The temporary result files can be much larger in size while solving compared to the final result file. Have at least 100GB+ of free space as the temporary results can balloon to many GBs in size for large/complex studies.

Consider investing in an NVMe (Non-Volatile Memory Express) SSD drive for additional performance. The NVMe interface was designed for SSD storage. This type of drive looks more like a memory chip. Standard SSDs have a matching form factor to HDDs so it could connect with the CPU using the legacy SATA (Serial AT Attachment) interface. NVMe drives are connected to the CPU with a high-speed PCIe socket.

Depending on the size/complexity of the study and which solver is being used, more memory may be required. For example the Direct Sparse solver in SOLIDWORKS Simulation uses roughly 5GB of RAM per 1 million DOFs (degrees of freedom). Best practices should be taken to reduce the DOFs as much as possible for faster solve times and to minimize the amount of memory required (i.e. mesh controls, symmetry, etc.).

Adding RAM to all memory slots in a computer can actually improve performance, though this does reduce the upgradability. Plan for current and future models. If you expect to get into larger projects at some point, consider installing additional memory.

While the graphics card does not improve the overall calculation time to solve the study, it does affect the time it takes to view the results. Having an old graphics card installed with an out-of-date date driver will cause slow performance and issues when trying to view the plots, especially animations. Be sure to have a SOLIDWORKS certified OpenGL workstation graphics card and install the certified driver. Read through our graphics card drivers article for more details.

Purchasing the highest end graphics card may sound like it will give you amazing performance, but the cost will be high for marginal improvement. Consider a mid-range graphics card to have the best balance. Read through our SOLIDWORKS System Requirement posts for more detail.

Vaadin and TouchKit themselves are quite lightweight. You can run a small web server like Jetty and simple Vaadin (or TouchKit) app with surprisingly light hardware. I have never even had a need to measure how little memory or cpu is actually needed. E.g. Liferay will require several times more. Your backend, applications architecture and amount of concurrent users will be in much more important role than TouchKit when estimating actual hardware requirements.

I usually run OptimusFlow on my monster desktop but I have a need to be mobile for a week. Can you give me an idea how much OptimusFlow will need in terms of resources hopefully without the cpu fan running full blast.

That being said, we do have our web-based trading platform, Optimus Trader: , that you are more than welcome to use as a backup to Optimus Flow. Optimus Trader is also free to all funded clients of Optimus Futures. Please keep in mind that this is a web-based platform and although it is not optimized for Mobile or does not have a native mobile application, it can be pulled up on a mobile phone to monitor your trading account and execute positions if needed.

The hardware requirements for Optimus Flow depends upon what you are doing with it. Most desktop systems can run Optimus Flow without any difficulty for basic, non-intensive features such as the DOM or your basic chart.

I prefer to run the trading software on a remote server, and remote desktop to it. That way the local laptop is always cool as no processing is done locally. I find lots of other advantages running that way as well, e.g. running the charting software in a data centre instead of locally means charts update more quickly.

The opinions expressed in these forums do not represent those of Optimus Futures, and any discussion of profit/loss is not indicative of future performance or success. Trading futures and options involves substantial risk of loss and is not suitable for all investors. Past performance is not necessarily indicative of future results. Optimus Futures, LLC is not affiliated with nor does it endorse any trading system, methodologies, newsletter or other similar service.

Most of the load on your nodes will be messages sent back and forth between other nodes on the network. Make sure you have a sufficiently fast connection; we recommend at least 1Gbps, and 5Gbps is better.

The bootstrapping scripts we'll use later are compiled binaries targeting an amd64 architecture, so your system must be 64-bit. Some of these scripts are bash based hence a shell interpreter that is bash compatible will also be needed.

You should also ensure you run time synchronization on the machine hosting the container, to avoid clock drift. In practice, this means configuring a client for the NTP protocol, and making sure it runs as a daemon. ntpd is one recommended example. To configure it, you just have to point it to an NTP server to query periodically. A default from your Linux distribution or cloud operator may already be set, and in the interest of decentralization, our recommendation would be to use it unless you have a specific reason to do otherwise.

Leap-smearing: Leap-smearing time servers and non-leap-smearing time servers are both acceptable for the magnitude of our time precision requirements - though considering very few providers offer leap smearing time servers, a "regular" time server helps ensure our pool of time providers is more diverse.

Why not do it in the container itself? Why do we need to do this?: Without special privileges and in all major container runtimes, a container will not run with the CAP_SYS_TIME capability. For Flow, this means that the node software itself cannot change the time of the host machine, making the in-container use of standard time synchronization protocols ineffective.

Why does time matter in Flow?: Time information comes up in consensus and in smart contracts. The consensus algorithm of Flow allows nodes to exit the influence of a corrupt or ineffective "leader" node by collectively deciding to switch to the next "phase" of the protocol at the right time. The smart contract language also allows developer access to block time stamps, which provide an approximation of time. To resist manipulation in each case, honest nodes must compute timing values from an aggregate of the information provided by all nodes. That approach, though resilient, is still sensitive to inaccurate time information. In other words, a node subject to clock drift but otherwise honest will not stop the consensus, but might make it slower.

Where the data is stored is up to you. By default, the systemd files that ship with Flow use /var/flow/data.This is where the vast majority of Flow's disk usage comes from, so you may wish to mount this directory on a separate disk from the OS.The performance of this disk IO is also a major bottleneck for certain node types.While all nodes need to make use of this disk, if you are running an execution node, you should make sure this is a high performing SSD.

Find current and previous version software and hardware requirements for operating systems, processors, memory, disk space, as well as recommendations for virtual machines and cloud computing services. For some products, you can see minimum or basic requirements, along with recommended components.

Get customized hardware solutions configured by engineers for engineers. GoEngineer has teamed up with Dell Technologies to provide fine-tuned workstations you can trust to meet the demands of your SOLIDWORKS designs.

A recommended OpenGL workstation graphics card and driver.

For a listing of recommended graphics cards and driver combinations visit the SOLIDWORKS System/Graphics Card Requirements Website.

-certification

Intel or AMD with SSE2 support. A 64-bit operating system required.

SOLIDWORKS can be made to run on Apple Mac based machines running under Parallels or BootCamp. It is not a recommended hardware configuration.

_ENU_HTML.htm

NOTE: Non-server products are only supported in the Parallels environment.

eDrawings is supported on Apple Macintosh-based machines.

3a8082e126