# How to optimise Jenkins Remoting for SCM plugin

**URL:** https://community.jenkins.io/t/how-to-optimise-jenkins-remoting-for-scm-plugin/35875
**Category:** Using Jenkins
**Tags:** remoting, question, docker
**Created:** [November 28, 2025, 4:37am UTC](https://community.jenkins.io/t/how-to-optimise-jenkins-remoting-for-scm-plugin/35875 "2025-11-28T04:37:14Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![anuragagarwal561994](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/anuragagarwal561994/32/18428_2.png) [@anuragagarwal561994](https://community.jenkins.io/u/anuragagarwal561994)
#### Post date: [November 28, 2025, 4:37am UTC](https://community.jenkins.io/t/how-to-optimise-jenkins-remoting-for-scm-plugin/35875/1 "2025-11-28T04:37:14Z")

</div>

Jenkins setup: `2.303.3-jdk8`

My setup involves running controller from my local machine and using kubernetes plugin to spawn agents in kubernetes cluster in production

I have got this setup using `ktunnel`

I read through how `remoting` works and hence cached the remoting jars in a persistent volume in my kubernetes cluster, and expecting them to load once by agent and next time the build should have been faster. But the SCM step takes a lot of time, for a simple step it takes 3 minutes to move to the next step.

The ping latency between my local machine and the cluster is 250 ms. Is there a way I can optimise this?

Note that I have even tried the setup with latest jenkins version, but it doesn’t still resolve the issue