On Wed, Mar 23, 2022 at 10:38 AM Casey Bodley <cbodley@xxxxxxxxxx> wrote: > > thanks Yehuda, > > On Wed, Mar 23, 2022 at 9:46 AM Yehuda Sadeh-Weinraub <yehuda@xxxxxxxxxx> wrote: > > > > On Tue, Mar 22, 2022 at 2:14 PM Adam C. Emerson <aemerson@xxxxxxxxxx> wrote: > > under a consistent write workload, rgw will currently broadcast these > notifications every 200ms by default (rgw_data_notify_interval_msec), > which seems excessively spammy to me - especially if data sync is > behind and we don't need the wakeups. if responsiveness on the order > of 5-10 seconds is sufficient, isn't it better to just increase the > polling frequency to match? > As I noted earlier in the thread, continuous polling *is* inconsistent with constantly notifying. I also agree that broadcasting every 200ms is questionable tuning, and so is the hard-coded 20s polling cycle on the other side. Again, why doesn't polling activity tend toward quiescence when there is no data change? Matt -- Matt Benjamin Red Hat, Inc. 315 West Huron Street, Suite 140A Ann Arbor, Michigan 48103 http://www.redhat.com/en/technologies/storage tel. 734-821-5101 fax. 734-769-8938 cel. 734-216-5309 _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
