CGRU Forum

Thank you! I will check this and report back.

Hallo, I am testing the current version 2.3.0 and in the server logs I get a lot: WARNING Client has NOT closed socket first. We are not using the web gui and I guess that you progammed the afrender to correctly close the socket. I have tried setting the option for SO_REUSEADDR to 1 according to htt...

Problem solved, I don't exactly know how. I just updated to HEAD and it went away.

Ok.

btw, how did you determine this is a good value for the stack?

Could I update our production server to the current master to get the fix? Is the "pools" feature working/doing something? Any other major changes since 2.2.1, that I need to check?

I have visualized the profiling. proc times are getting higher the longer it runs.




and at some point the server just hangs. times are dropping to 6ms and no further connection possible. I have to restart it then.

via json I can save objects to the store: { "save": { "path" : "saved_object", "":"path will be related to CGRU_LOCATION and .json extension will be added", "object": { "prop_a":"value A", "prop_b":"value ...

I changed it and get about 10ms for proc now (which was constantly 0 before). I also noticed that there were 2 other afserver instances running (for whatever reason) maybe they are making the high times....

Could it be there is a bug in the profiler? From the code profiler.cpp Line 108: double prep = 0.0; double proc = 0.0; double post = 0.0; for( int i = 0; i < ms_profiles.size(); i++) { prep += toFloat( ms_profiles[i]->m_tstart ) - toFloat( ms_profiles[i]->m_tinit ); proc += toFloat( ms_profiles[i]->...

load average is 0.56, the host (8 core 16Gb) is pretty bored. There are 600 jobs in the queue, 17 rendering, 20 ready.