xfygogo
/
phasicFlow
mirror of https://github.com/PhasicFlow/phasicFlow.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #220 from wanqing0421/benchmarks 

update readme
This commit is contained in:
PhasicFlow 2025-04-27 21:57:40 +03:30 committed by GitHub
parent c0d12f4243 8b5d14afe6
commit cd051a6497
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
5 changed files with 37 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
benchmarks/rotatingDrum/images/Calculation time under different particle numbers using commerical DEM and phasicFlow.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 MiB

BIN
benchmarks/rotatingDrum/images/Memory usage under different particle numbers using commerical DEM and phasicFlow.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 MiB

BIN
benchmarks/rotatingDrum/images/commerical DEM snapshot.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 549 KiB

BIN
benchmarks/rotatingDrum/images/phasicFlow snapshot.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 387 KiB

52
benchmarks/rotatingDrum/readme.md
View File

@ -1,27 +1,35 @@
# Benchmarks of rotating drum (v-1.0)
## Problem definition
Compare the computational efficiency by rotatingDrum tutorials using phasicFlow in different calculation loads. The calculation time and memory usage when the number of particles tested was 250 k, 500 k, 1 m, 2 m, 4 m and 8 m.
**The rotatingDrum case was calculated using well-known discrete element commercial software and phasicFlow, and the calculation time and memory usage were tested when the number of particles was 250 k, 500 k, 1 m, 2 m, 4 m and 8 m.**
<div align="center">
<b>
A view of rotating drum
</b>
<b>
<img src="./images/commerical DEM snapshot.png" alt="description" width="400" />
</div>
![](https://github.com/PhasicFlow/phasicFlow/blob/media/media/rotating-drum-s.png)
</b></div>
<div align="center">Figure 1. The snapshot of commerical DEM simulation</div>
<div align="center">
<img src="./images/phasicFlow snapshot.png" alt="description" height="600" />
</div>
<div align="center">Figure 2. The snapshot of phasicFlow simulation</div>
**The performance tests were conducted on laptop computers and workstation computers respectively. The configuration information of the laptop computers and workstation computers is shown in Table 1.**
Performance tests were conducted separately on laptops and workstations, and the configuration information for laptops and workstations is shown in Table 1.
<div align="center">Table 1. The parameters of laptop and workstation.</div>
| computer | CPU | GPU | Operating system |
| :---------: | :----------------------: | :--------------------------: | :--------------: |
| Laptop | Intel i9-13900HX 2.2 GHz | NVIDIA Geforce RTX 4050Ti 6G | Ubuntu 22.04 |
| Laptop | Intel i9-13900HX 2.2 GHz | NVIDIA Geforce RTX 4050Ti 6G | Windows 11 24H2 |
| workstation | Intel xeon 4210 2.2 GHz | NVIDIA RTX A4000 16G | Ubuntu 22.04 |
**A total of 6 groups of working condition tests were carried out, with the particle numbers being 250 k, 500 k, 1 m, 2 m, 4 m and 8 m respectively. The particle diameter, drum length and drum diameter under each working condition are shown in Table 2.**
A total of 6 sets of operating condition tests were conducted, with particle quantities of 250 k, 500 k, 1 m, 2 m, 4 m and 8 m in sequence, the particle diameter, drum length, and drum diameter under each operating condition are shown in Table 2.
<div align="center">Table 2. The parameters setting of different rotating drum.</div>
| Case name | Particle diameter | Particle numbers | Rotating drum length | Rotating drum radius |
@ -33,22 +41,36 @@ A total of 6 sets of operating condition tests were conducted, with particle qua
| 4 m | 3 mm | 4,000,000 | 1.6 m | 0.2 m |
| 8 m | 2 mm | 8,000,000 | 1.6 m | 0.2 m |
Table 3 shows the calculation time of phasicFlow under different operating conditions on laptops and desktops. It can be seen from the table that the increase in calculation time is linearly proportional to the increase in particle count. Using an A4000 graphics card results in a calculation speed approximately 30% faster than using a 4050Ti.
**Table 3 and Figure 3 show the calculation time of phasicFlow and well-known discrete element commercial software under different working conditions on a laptop. It can be seen from the table that the increase in calculation time is linearly proportional to the increase in the number of particles. The calculation speed of phasicFlow is about 20% faster than that of well-known discrete element commercial software. The calculation speed of using A4000 graphics card is about 30% faster than that of 4050Ti.**
<div align="center">Table 3 The calculation time of phasicFlow.</div>
<div align="center">Table 3 The calculation time of different software.</div>
| Software | 250 k | 500 k | 1 m | 2 m | 4 m | 8 m |
| :---------------: | :----: | :-----: | :-----: | :-----: | :-----: | :------: |
| phasicFlow-4050Ti | 54 min | 111 min | 216 min | 432 min | | |
| commerical DEM-4050Ti | 68 min | 136 min | 275 min | 570 min | | |
| phasicFlow-A4000 | 38 min | 73 min | 146 min | 293 min | 589 min | 1188 min |
<div align="center">
<img src="./images/Calculation time under different particle numbers using commerical DEM and phasicFlow.png" alt="description" height="600" />
</div>
Table 4 shows the memory usage of phasicFlow under different operating conditions on laptops and workstations. According to the table, phasicFlow uses approximately 0.7 GB of memory per million particles.
<div align="center">Figure 3 The calculation time of different software.</div>
<div align="center">Table 4 The memory usage of phasicFlow.</div>
**Table 4 and Figure 4 show the memory usage of phasicFlow and well-known discrete element commercial software on a laptop under different working conditions. It can be seen from the table that phasicFlow uses about 0.7 GB of memory per million particles, while the well-known discrete element commercial software uses about 1.2 GB of memory per million particles.**
<div align="center">Table 4 The memory usage of different software.</div>
| Software | 250 k | 500 k | 1 m | 2 m | 4 m | 8 m |
| :---------------: | :-----: | :-----: | :-----: | :-----: | :-----: | :-----: |
| phasicFlow-4050Ti | 252 MB | 412 MB | 710 MB | 1292 MB | | |
| commerical DEM-4050Ti | 485 MB | 897 MB | 1525 MB | 2724 MB | | |
| phasicFlow-A4000 | 344 MB | 480 MB | 802 MB | 1386 MB | 2590 MB | 4966 MB |
<img src="./images/Memory usage under different particle numbers using commerical DEM and phasicFlow.png" alt="description" height="600" />
<div align="center">Figure 4 The memory usage of different software.</div>