# Processing background jobs (Windows Service) affects load of ASP.NET Web API

**URL:** <https://discuss.hangfire.io/t/processing-background-jobs-windows-service-affects-load-of-asp-net-web-api/3691>\
**Category:** question\
**Created:** [August 15, 2017, 7:02am UTC](https://discuss.hangfire.io/t/processing-background-jobs-windows-service-affects-load-of-asp-net-web-api/3691 "2017-08-15T07:02:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![robing6](https://avatars.discourse-cdn.com/v4/letter/r/ccd318/32.png) [@robing6](https://discuss.hangfire.io/u/robing6)\
**Post date:** [August 15, 2017, 8:29am UTC](https://discuss.hangfire.io/t/processing-background-jobs-windows-service-affects-load-of-asp-net-web-api/3691/2 "2017-08-15T08:29:52Z")

</div>

Allright, so I found the issue after seeing this comment: [Hangfire causes application performance issue](http://hangfire.discourse.group/t/hangfire-causes-application-performance-issue/809/5?u=robing6)

I did some file caching within the bin folder of my [ASP.NET](http://ASP.NET) Web API, which caused the API to wait apparently for the IO to finish. I moved the file caching to somewhere outside my bin folder and it seems to work like a charm now.

---

_[View the full topic](https://discuss.hangfire.io/t/processing-background-jobs-windows-service-affects-load-of-asp-net-web-api/3691)._