Slow execution speeds and repeated output
See original GitHub issueProviders utilizing the utils.custom_code method perform slowly and output the same value several times when called repeatedly from the same program.
To replicate, update the comp.py file by replacing p.full_name() with p.telephone('###-###-####') on line 27. If you change the count to something small, say 50, and print out the output of p.telephone('###-###-####'), you’ll see that many of the generated phone numbers are identical.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
What Is Slow Processing Speed? - Understood.org
Slow processing speed is when people need a lot of time to take in, make sense of, and respond to information. The information...
Read more >Do speeds of if statements in a repetitive loop affect overall ...
A slightly longer answer: It won't matter unless the loop is run millions of times and the other statement in it is actually...
Read more >VI Execution Speed - NI - National Instruments
This section discusses factors that affect execution speed and ... Examine the following items to determine the causes of slow performance:.
Read more >Troubleshooting Slow Running Flows - Microsoft Support
Cause. There are number of possible causes to slow running flows: The service you are connecting to is running slowly. For instance, a...
Read more >Data simple - Speed up R - Luis Vale Silva
A major speed bottleneck in this code is caused by the repeated use of rbind() . The function rbind() is slow, particularly as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Yeap, it really should. @gardnerjh thanks for this issue, it is already fixed in the newest version.
@sobolevn So, version 1.0.0 should work correctly, because i have fixed this issue a few days ago, here: utils.custom_code.