iccsa-19-vtestbed

git clone https://git.igankevich.com/iccsa-19-vtestbed.git
Log | Files | Refs

commit 753d84c9bc8b24ca9f9f20b42569eaaf6b09f6c2
parent 9e7afbf5909abe3792d649d9a533fc70db1a0a2f
Author: Ivan Gankevich <igankevich@ya.ru>
Date:   Thu, 28 Mar 2019 15:56:31 +0300

Discuss ship hull size.

Diffstat:
main.tex | 17+++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/main.tex b/main.tex @@ -498,14 +498,15 @@ with high frame rate and small simulation time steps. \item Usage of graphical accelerator increases time needed to synchronise simulation step with the visualisation frame (\textit{exchange} stage in fig.~\ref{fig:histogram}). - + \end{itemize} \begin{table} \centering - \caption{Best median performance for each workstation (sphere). Here \(t\) - is simulation step computation time, \(m\)~--- no. of simulation steps per - second (SSPS), and \(n\)~--- the number of OpenMP threads.\label{tab:best}} + \caption{Best median performance for each workstation and each ship hull. + Here \(t\) is simulation step computation time, \(m\)~--- no. of simulation + steps per second (SSPS), and \(n\)~--- the number of OpenMP + threads.\label{tab:best}} \begin{tabular}{lrrrlrrrlrrrl} \toprule & \multicolumn{4}{c}{Sphere} @@ -577,6 +578,14 @@ particular dangerous situation (e.g.~large roll angle) and try to prevent it by notifying ship's crew and an operator on the coast. This is one of the topics of future work. +Overall performance depends on the size of the ship rather than the number of +panels. MICW hull has less number of panels than Aurora, but larger size and +exactly two times worse performance (tab.~\ref{tab:best}). The size of the hull +affects the size of the grid in each point of which velocity potential and then +pressure is computed. These routines are much more compute intensive in +comparison to wetted surface determination and pressure force computation +(performance of which depends on the number of panels). + Despite the fact that Capybara has the highest floating-point performanace across all workstations in the benchmarks, Virtual testbed runs faster on its processor, not the graphical accelerator. Routine-by-routine investigation