KAPOW

Welcome to the Kapow forum. Here you can get help, use your skills to help others and enjoy hanging out in the company of other Kapow Robot Developers.


Out of Memory issue.

Share
avatar
Shyam Kumar
Ranks

Posts : 76
Points : 1682
Join date : 2013-07-05
Location : Kerala, India

Out of Memory issue.

Post by Shyam Kumar on Mon Aug 11, 2014 1:32 pm

When i run multiple robots in Design Studio, it will shows a message box like "Out of Memory" and restart Design studio automatically.. Any one can tell why it will happen?, What are the solutions for avoid this issue?..
I attached the message box also..


Thanks


Last edited by Shyam Kumar on Thu Jul 14, 2016 10:51 am; edited 2 times in total
avatar
Shyam Kumar
Ranks

Posts : 76
Points : 1682
Join date : 2013-07-05
Location : Kerala, India

Re: Out of Memory issue.

Post by Shyam Kumar on Thu Jun 25, 2015 6:03 pm

After a long  research finally i found the issue and solution. I believe it will help anyone. The default design studio instance provided by kapow is 6 and we can increase the instance of kapow design studio up to 50. But its working based on the memory. The default memory allocation of Kapow katalyst is 1024 (1GB). Some websites taking too much time for loading page or some scripts or specific action steps in robots taking too much memory.. This time a specific robot will take too much memory, and that time kapow design studio uses maximum available memory.. this is the reason for kapow design studio automatically restarted..


We can solve this issue with increasing the memory of Kapow Design studio.

In kapow design studio open bin--> and open DesignStudio.conf file --> and change the memory in wrapper.java.maxmemory=1024 (#wrapper.java.maxmemory=3072) and save the file, then restart the kapow design studio.
avatar
Shyam Kumar
Ranks

Posts : 76
Points : 1682
Join date : 2013-07-05
Location : Kerala, India

How to reduce robot memory utilization

Post by Shyam Kumar on Thu Jul 14, 2016 10:49 am

When a robot runs on a RoboServer, it saves a a snapshot of its state, the browser state and variables state before each of these:

- a Loop step
- a Try step
- a branch point

Depending on different conditions in the following steps, the robot might need to come back to these elements. When this happens, the robot will restore the snapshot taken before the step and will be able to continue execution.

E.g. In a loop, after each iteration, the robot loads the initial snapshot and can execute the next iterations without being influences by the previous one.
In robots with multiple branches the robot will restore the initial state each time it comes back to a branch point or a try step (so after all steps from the previous branch are executed).

However, the more snapshots the robot has to take, the more memory it needs. Therefore, if the number of try steps, loops, branch points is reduced, the memory usage is reduced. It is not always possible to reduce the number of try steps, loops and branches.



Reducing the number of try steps has improved robot execution.
avatar
Shyam Kumar
Ranks

Posts : 76
Points : 1682
Join date : 2013-07-05
Location : Kerala, India

Re: Out of Memory issue.

Post by Shyam Kumar on Wed Aug 10, 2016 3:23 pm

  

  Memory consumption, like always, is dependent on the required bandwidth in terms of parallel robots needed for a specific project.


     However, some robots consume more memory than others. Large Excel spreadsheets for example or large XML files consume incredible amounts of memory.

     One major pitfall in terms of memory footprint is that RoboServer is not restricted by the memory assigned to the JVM, when you run WebKit robots. That means that where you could be led to believe that configuring a dedicated RoboServer-machine to let the RoboServer JVM consume all the available physical memory is a good approach, in fact it is not (if you want to run any WebKit robots). You need to leave some physical memory available for the kapowbrowser processes.

Between 9.3 and 9.4 the memory footprint (in terms of virtual memory) of the individual kapow (WebKit) browser process was significantly reduced.

Kapow 9.5 features monitoring (through Management Console) of the individual RoboServer’s total memory and CPU consumption, including the memory consumed by the kapowbrowser sub-processes. That should help system integrators determine at which velocity robots can be safely run and/or how much memory to assign to the machine running RoboServer.
avatar
Shyam Kumar
Ranks

Posts : 76
Points : 1682
Join date : 2013-07-05
Location : Kerala, India

Memory consumption

Post by Shyam Kumar on Fri Oct 07, 2016 2:55 pm

     Memory consumption is dependent on the required bandwidth in terms of parallel robots needed for a specific project.
However, some robots consume more memory than others. Large Excel spreadsheets for example or large XML files consume incredible amounts of memory.
One major pitfall in terms of memory footprint is that RoboServer is not restricted by the memory assigned to the JVM, when you run WebKit robots. That means that where you could be led to believe that configuring a dedicated RoboServer-machine to let the RoboServer JVM consume all the available physical memory is a good approach, in fact it is not (if you want to run any WebKit robots). You need to leave some physical memory available for the kapowbrowser processes.
Between 9.3 and 9.4 the memory footprint (in terms of virtual memory) of the individual kapow (WebKit) browser process was significantly reduced.
Kapow 9.5 features monitoring (through Management Console) of the individual RoboServer’s total memory and CPU consumption, including the memory consumed by the kapowbrowser sub-processes. That should help system integrators determine at which velocity robots can be safely run and/or how much memory to assign to the machine running RoboServer.

Anci Aziz

Posts : 2
Points : 1487
Join date : 2013-08-28

Re: Out of Memory issue.

Post by Anci Aziz on Tue Jan 03, 2017 11:54 am

hi shyam,

             This is solved in higher versions of kapow, you can update the latest version to avoid memory issues at some extend...

    Current date/time is Fri Sep 22, 2017 2:27 am