Title: Read data in bulks for non-foreground reporters · Issue #91 · utPLSQL/utPLSQL-java-api · GitHub
Open Graph Title: Read data in bulks for non-foreground reporters · Issue #91 · utPLSQL/utPLSQL-java-api
X Title: Read data in bulks for non-foreground reporters · Issue #91 · utPLSQL/utPLSQL-java-api
Description: Currently, when running tests with coverage, where the data produced by coverage report is large, each reporter is most probably running a row-by-row query from client to DB. We should prevent this as it significantly impacts the overall...
Open Graph Description: Currently, when running tests with coverage, where the data produced by coverage report is large, each reporter is most probably running a row-by-row query from client to DB. We should prevent this...
X Description: Currently, when running tests with coverage, where the data produced by coverage report is large, each reporter is most probably running a row-by-row query from client to DB. We should prevent this...
Opengraph URL: https://github.com/utPLSQL/utPLSQL-java-api/issues/91
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Read data in bulks for non-foreground reporters","articleBody":"Currently, when running tests with coverage, where the data produced by coverage report is large, each reporter is most probably running a row-by-row query from client to DB.\r\n\r\nWe should prevent this as it significantly impacts the overall execution time of run when done va utPLSQL-cli.\r\n\r\nIdeally, data from reporters that do not report to screen but do reporting in background , should be read in bulks of 100, 1000 or even 10000 rows.\r\n\r\nIf you have a look at our test runs on Travis, \r\n~50 seconds is time for utPSLQL unit test run, while overall end-to-end run takes ~80 seconds.\r\nI can imagine that on really large schema, most of the time might be spent on reading coverage report by cli.","author":{"url":"https://github.com/jgebal","@type":"Person","name":"jgebal"},"datePublished":"2019-07-17T01:23:38.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/91/utPLSQL-java-api/issues/91"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:604a7edb-1704-ade6-e53a-60d6424cfdf4 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | EE00:2946F1:23BC34E:2E6F7E0:696D8E82 |
| html-safe-nonce | 1444ded24f401d1e9a649a57dc01ccbe462afdf35895fd4bf49ffab7ecd0458b |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFRTAwOjI5NDZGMToyM0JDMzRFOjJFNkY3RTA6Njk2RDhFODIiLCJ2aXNpdG9yX2lkIjoiNzIwNjgzNjI5NTU5NjYwOTE1NCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 81707c23faf94fc3f69b7ac8030a6d3e6c238b52dbf50fe3f1be6dc1109c6a53 |
| hovercard-subject-tag | issue:468940266 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/utPLSQL/utPLSQL-java-api/91/issue_layout |
| twitter:image | https://opengraph.githubassets.com/5e24b8e55fadd7d4d39fe61b39fbf63f66fc0123ff4647308023a64586de69d8/utPLSQL/utPLSQL-java-api/issues/91 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/5e24b8e55fadd7d4d39fe61b39fbf63f66fc0123ff4647308023a64586de69d8/utPLSQL/utPLSQL-java-api/issues/91 |
| og:image:alt | Currently, when running tests with coverage, where the data produced by coverage report is large, each reporter is most probably running a row-by-row query from client to DB. We should prevent this... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | jgebal |
| hostname | github.com |
| expected-hostname | github.com |
| None | 4922b452d03cd8dbce479d866a11bc25b59ef6ee2da23aa9b0ddefa6bd4d0064 |
| turbo-cache-control | no-preview |
| go-import | github.com/utPLSQL/utPLSQL-java-api git https://github.com/utPLSQL/utPLSQL-java-api.git |
| octolytics-dimension-user_id | 15661281 |
| octolytics-dimension-user_login | utPLSQL |
| octolytics-dimension-repository_id | 86466023 |
| octolytics-dimension-repository_nwo | utPLSQL/utPLSQL-java-api |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 86466023 |
| octolytics-dimension-repository_network_root_nwo | utPLSQL/utPLSQL-java-api |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 7e5ae23c70136152637ceee8d6faceb35596ec46 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width