Vyshali, Jython itself is known to be relatively slow, so using the scripting processors you'll always be up against that. I see a couple of options to improve performance:
1) Use InvokeScriptedProcessor (ISP) instead of ExecuteScript. ISP is faster because it only loads the script once, then invokes methods on it, rather than ExecuteScript which evaluates the script each time. I have an ISP template in Jython [1] which should make porting your ExecuteScript code easier. 2) Use ExecuteStreamCommand with command-line Python instead. You won't have the flexibility of accessing attributes, processor state, etc. but if you're just transforming content you should find ExecuteStreamCommand with Python faster. Regards, Matt [1] http://funnifi.blogspot.com/2017/11/invokescriptedprocessor-template.html On Sun, Nov 12, 2017 at 7:31 PM, Vyshali <[email protected]> wrote: > Hi Matt, > > I'm using Jython in executescript because of my requirement.I cant switch to > groovy because I'm using packages supported by Python.Is there any way to > increase the speed of the executescript processor.Please help me with your > ideas. > > Thanks, > Vyshali > > > > -- > Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
