Yes, it's one way but it's not flexible, and scale app need to restart the app as well.
toggle quoted messageShow quoted text
As I said I may have some heavy operations which will definitely need more than 2G.
In my opinion the ideal way is that we just set a maximum value for each process, but during the running of the process, we don't pre-allocate the memory as we specify as the maximum in deployment.
I suggest you manually “cf scale -m 2G“ after your app has booted.
Type “cf scale --help” for more info.
Le 9 mars 2016 à 04:09, Stanley Shen <meteorping(a)gmail.com> a écrit :application, but in most time, we don't need so much memory.
When pushing an application to CF, we need to define its disk/memory limitation.
The memory limitation is just the possible maximum value will be needed in this
For example, I have one application which needs at most 5G memory at startup somesome specific operation, but in most time it just needs 2G.
So right now I need to specify 5G in deployment manifest, and 5G memory isallocated.
applications, like 3 since only 2G is needed for each application.
Take m3.large VM for example, it has 7.5G.
Right now we can only push one application on it, but ideally we should can push more
will not be released even I stopped the application.
Can the resources of a IDLE application be shared by other applications?
It seems right now all the resources are pre-allocated when pushing application, it