🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.
Join and Win

Optimization is really slow

User: "Pedro Neves"
Altair Community Member
Updated by Pedro Neves

Hi,

I'm having problems with the topology optimization of one brake pedal that I'm trying to optimize. It seems to be all ok with the model, but when I try to run Optistruct the process is really slow, like 30 minutes per interation and my model is relatively simple. I have no idea of what could be causing the problem here, because I did an analysis to see if it was all ok and it seemed to be all fine.

I'll have atached my model so you can try to help me and find what is my problem here.

Thanks

Unable to find an attachment - read this blog

Find more posts tagged with

Sort by:
1 - 9 of 91
    User: "Altair Forum User"
    Altair Employee
    Updated by Altair Forum User

    Hi Pedro Neves,

     

    I think it might be because of your system configuration. We are able to run it quickly at our end.

    Please can you tell us which version of Solver you are using and configurations of your system

     

     

    Thank you

    User: "Pedro Neves"
    Altair Community Member
    OP
    Updated by Pedro Neves

    Sorry @Premanand Suryavanshi I didn't received the notification of your reply and I only went to see my posts now. 

    I am using the version of solvers 2018.0.1 (hotfix). In the beggining of my optimization, in Optistruct, the values of progress and iteration progress seem to be always struck in 2% and 62%, correspondingly. Ãfter a while, the optimization advances to the next iteration. And then, if I open the results in the end, they are very poor and show almost or completely nothing.

    What do you mean with configurations of my system?

     

    User: "Pedro Neves"
    Altair Community Member
    OP
    Updated by Pedro Neves

    @Premanand Suryavanshi can you answer my post please?

    User: "QuyNguyenDai"
    Altair Community Member
    Updated by QuyNguyenDai

    How about your hardware? CPU? Mem? Do you run in parallel?

    User: "Rahul Rajan_21763"
    New Altair Community Member
    Updated by Rahul Rajan_21763

    In my laptop it took less than two minutes.Please share above requested details.

    Unable to find an attachment - read this blog

    User: "Pedro Neves"
    Altair Community Member
    OP
    Updated by Pedro Neves

    My laptop it's an Asus ROG GL552VW, I think it has good hardware. i7 6700HQ Processor, SDRAM 8Gb.

    What happened was weird, because in my first times it went well, but after some weeks of using the version I have now happened what I described in my later post

    User: "Rahul Rajan_21763"
    New Altair Community Member
    Updated by Rahul Rajan_21763

    Please check attached documents for platform support and hardware recommendation.

    Unable to find an attachment - read this blog

    User: "Sy Nguyen Van"
    Altair Community Member
    Updated by Sy Nguyen Van

    Hello Pedro Neves,

    I got the same problem as you.

    For me, this issue comes from the location of the model files. I placed model files in GOOGLE DRIVE, thus it takes me 6 hours to complete the one simple optimization. 

    Luckily, then I move model files to Download or Desktop, and it will run as normal.

    I hope it will help you or others in the future.

    Best,

    User: "Adriano_Koga"
    Altair Employee
    Updated by Adriano_Koga

    Hello Pedro Neves,

    I got the same problem as you.

    For me, this issue comes from the location of the model files. I placed model files in GOOGLE DRIVE, thus it takes me 6 hours to complete the one simple optimization. 

    Luckily, then I move model files to Download or Desktop, and it will run as normal.

    I hope it will help you or others in the future.

    Best,

    using a network or cloud drive is not recommended, as the solver needs to write and read data from your model location (scratch).

    But for OptiStruct, 2 aspects are important:

    - model size vs RAM memory available (need to take into account the memory used by other applications and windows, for example) >> if RAM is not enough, the modelwill use less RAM, BUT try to use more hard disk

    - scratch data is written and read for temporary data, and specially if not enough RAM memory is available, it will be necessary much more space for scratch in the hard disk. Problem is, if the scratch access is slow (slow hard drive, or network drive), your run will take longer.