← Back to team overview

yade-users team mailing list archive

Re: Simulation with 100,000 sphere

 

Hi,

I also need to do large scale simulation which may need to do around 500,000
for field engineering case. but instead of using YADE I have to develop my
own code to do this, :(.
In my opinion, the CPU computing time is the most important issue in DEM,
while the memory is determined by the total particle number, and you
data-structure design, 2GB can do a lot for a 2D case, for 3D case you may
need more memory. but the momory requirements will not change much when your
total particle number is defined.

hi, Vaclav,
is it possible that the 5 mins used for packing or sample preparation to
fill the container? I just guess, for my case, it takes some time for this
step and then enter the cycling.

Wishes.

Kan


On 2/24/08, yade-users-request@xxxxxxxxxxxxxxxx <
yade-users-request@xxxxxxxxxxxxxxxx> wrote:
>
> Send Yade-users mailing list submissions to
>        yade-users@xxxxxxxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.berlios.de/mailman/listinfo/yade-users
> or, via email, send a message with subject or body 'help' to
>        yade-users-request@xxxxxxxxxxxxxxxx
>
> You can reach the person managing the list at
>        yade-users-owner@xxxxxxxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Yade-users digest..."
>
>
> Today's Topics:
>
>   1. Simulation with 100,000 sphere (Kien Dang, Mr)
>   2. Re: Simulation with 100,000 sphere (milauer <eudoxos@xxxxxxxx>)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 23 Feb 2008 21:35:31 -0500
> From: "Kien Dang, Mr" <kien.dang@xxxxxxxxxxxxxx>
> Subject: [Yade-users] Simulation with 100,000 sphere
> To: <yade-users@xxxxxxxxxxxxxxxx>
> Message-ID:
>        <
> BE1A3E6D6B8F8047B1C72C2F4F3FFC8A49AD2E@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain;       charset="iso-8859-1"
>
> Hi all,
>
> Have anyone ever run a simulation with 100,000 spheres? I run one with my
> desktop and it takes forever for one loop. I let it run 4 hours and no thing
> happen (in null GUI). My desktop is AMD 6400, 2gb RAM,
>
> Thanks,
>
> Kien Dang
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 24 Feb 2008 10:43:12 +0100
> From: V?clav S(milauer <eudoxos@xxxxxxxx>
> Subject: Re: [Yade-users] Simulation with 100,000 sphere
> To: yade-users@xxxxxxxxxxxxxxxx
> Message-ID: <47C13C30.1050206@xxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
> >
> > Have anyone ever run a simulation with 100,000 spheres? I run one with
> my desktop and it takes forever for one loop. I let it run 4 hours and no
> thing happen (in null GUI). My desktop is AMD 6400, 2gb RAM,
> >
> Hi, I was recently running (for speed measurements) TriaxialTest with
> 40000 elements. It took maybe 5 minutes before the simulation started,
> then it ran at steady speed. The figure linked below shows #elements and
> time per iteration graph, it is nicely linear, so I would expect about 1
> iteration / sec with 100000 spheres at my computer (slower than yours).
> RAM requirements are negligible, I didn't notice any bump on the RAM
> monitor in the panel.
> beta.arcig.cz/~eudoxos/temp/yade-triax-speed@xxxxxxxxxxxxxxxxxxxxxxxxx
>
> I didn't investigate what was the cause of the lag at the beginning -
> either root body initializers or first run of the SAP collider that has
> to fill its bound containers. I may profile that with kcallgrind, but I
> fear in that case those 5 minutes would take forever.
>
> Regards, Vaclav
>
>
>
> ------------------------------
>
> _______________________________________________
> Yade-users mailing list
> Yade-users@xxxxxxxxxxxxxxxx
> https://lists.berlios.de/mailman/listinfo/yade-users
>
>
> End of Yade-users Digest, Vol 20, Issue 14
> ******************************************
>
_______________________________________________
Yade-users mailing list
Yade-users@xxxxxxxxxxxxxxxx
https://lists.berlios.de/mailman/listinfo/yade-users

Follow ups