Reported by rbrewer, Mar 31, 2010
The WattDepot server seems to generate a lot of CPU usage. Some of this is presumably due to the lack of caching for calculated values, but it seems excessive even for that. Better logging (of each HTTP request for instance) would be helpful in tracking this down. There is already logging on the REST API side, but nothing on the data source API side, which is where most of the requests are coming at this point.
Reported by rbrewer, Mar 31, 2010 The WattDepot server seems to generate a lot of CPU usage. Some of this is presumably due to the lack of caching for calculated values, but it seems excessive even for that. Better logging (of each HTTP request for instance) would be helpful in tracking this down. There is already logging on the REST API side, but nothing on the data source API side, which is where most of the requests are coming at this point.