Forum Discussion

Jane_Lau_106245's avatar
Jane_Lau_106245
Icon for Nimbostratus rankNimbostratus
Jun 30, 2006

Do you see any problem of doing CONFIGSYNC_BASIC in a grid environment?

We have a java app that will configure virtual servers, irules, pools, nodes, and monitors on behave of other servers. There can be times when thousands of nodes/servers trying to talk to our java app. We do configsync for each server request so I’m wondering whether this’ll cause any performance issues. The reason for doing configsync for each request is lack of knowledge when is the best time to do it. BTW, the requests can come-in in any fashions (the worst case is all at one time). Our two java app servers are also load-balanced through BigIP. Sorry for the lengthy note.
dev
devops
iControl

1 Reply

Sort By
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Jul 05, 2006
    Are you referring to saving the configuration locally (via. System::save_configuration) or synchronizing across to a secondary device. For local configuration, you should be able to issue a save_configuration with CONFIGSYNC_BASIC on each change request with minimal overhead. The GUI does this with every page change so doing it programmatically will have the same overhead as using the GUI.

     

     

    If you are referring to syncing to a partner device, then that has a bit more overhead to it and should be done sparingly depending on your usage patterns.

     

     

    -Joe