Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ftd:0.3: Performance Testing #533

Closed
AbrarNitk opened this issue Jan 16, 2023 · 9 comments · Fixed by fastn-stack/fastn-old#733 or #532
Closed

ftd:0.3: Performance Testing #533

AbrarNitk opened this issue Jan 16, 2023 · 9 comments · Fixed by fastn-stack/fastn-old#733 or #532

Comments

@AbrarNitk
Copy link
Contributor

AbrarNitk commented Jan 16, 2023

This issue is related to checking performance for both fpm and ftd, where I take different files of ftd and serve them via fpm and capture the performance logs.

I have taken benchmarking according to different syntax and components, please check below.

@AbrarNitk
Copy link
Contributor Author

AbrarNitk commented Jan 16, 2023

Hardware and OS Info

OS: MacBook Pro Ventura 2020
Processor: M1 Chip
Memory: 16GB

About FPM and FTD

FPM PR: fpm-tracing/with-ftd-tracing
FTD PR: ftd-tracing
Using actix-web as HTTP server in FPM

ftd.dev index.ftd testing details

extra downloads like FPM.ftd files for other projects
if .packages are not available
html size: 1.2MB
browser latency: 9s
fpm serve: 834ms
read_ftd_2022: 811ms

second time call
html size: 1.2MB
browser latency: 345ms
fpm serve: 266ms
read_ftd_2022: 258ms

Static Image Testing

  • static image which is available on file system
  • ftd.dev logo-fifthtry-dark.svg

size: 3.1kB
browser latency: 54ms

Dark Image Testing

  • ftd.dev hamburger-dark.svg
  • very less size but taking more time, fpm is downloading it from github

size: 716B
browser latency: 717ms
fpm serve: 30ms
Config::read: 17ms
file-system-call: <1ms
resolve: 3ms
network download call time: 9ms

while serving from filesystem
size: 716B
browser latency: 57ms
fpm serve: 24.2ms
Config::read: 21ms
file system call: 3ms

fpm.dynamic-urls Testing

tested with four named params in the fpm.dynamic-urls with 1000 entries in zigzag fashion

ex: /<string:username>/<string:class>/<integer:age>/<boolean:flag>/
fpm serve: 26.2ms
Config::read: 18ms
dynamic-urls-resolve-document: 100 micro seconds
read ftd: 6ms

fpm.sitemap Testing

with 2k entries in the sitemap with zigzag combination of Urls

fpm serve: 28.6ms
Config::read: 15ms
sitemap-resolve-document: 2.10ms
read ftd: 7.11ms (only contains one -- ftd.text)

With 1K -- ftd.text

Logs

total: 196ms
interpret_with_line_number: 134ms, taking most of the time
from_interpreter: 25ms
from_rt: 4ms
from_node_data: 9ms

### Server Started ###
Go to: http://127.0.0.1:8000
### Configured tracing ###
INFO  i [info]: Starting 8 workers
INFO  i [info]: Tokio runtime found; starting in existing Tokio runtime
replace_markers in 547.25µs
INFO  route [ 196ms | 0.76% / 100.00% ]
INFO  ┝━ i [info]:  | method: "GET" | uri: "/1k-text/"
INFO  ┕━ serve [ 195ms | 0.12% / 99.24% ]
INFO     ┝━ Config::read [ 21.1ms | 10.75% ]
INFO     ┝━ serve_file [ 173ms | 0.13% / 88.37% ]
INFO     │  ┝━ get_file_and_package_by_id [ 125µs | 0.05% / 0.06% ]
INFO     │  │  ┝━ i [info]:  | path: "1k-text/"
INFO     │  │  ┕━ resolve_by_id [ 29.7µs | 0.01% / 0.02% ]
INFO     │  │     ┝━ i [info]:  | id: "1k-text/"
INFO     │  │     ┕━ fs_fetch_by_id [ 18.2µs | 0.00% / 0.01% ]
INFO     │  │        ┕━ fs_fetch_by_file_name [ 14.4µs | 0.01% ]
INFO     │  │           ┕━ i [info]:  | document: "1k-text.ftd"
INFO     │  ┕━ read_ftd [ 173ms | 0.00% / 88.18% ]
INFO     │     ┝━ i [info]:  | document: "1k-text.ftd"
INFO     │     ┕━ read_ftd_2022 [ 173ms | 0.52% / 88.18% ]
INFO     │        ┝━ interpret_helper [ 134ms | 0.20% / 68.59% ]
INFO     │        │  ┝━ i [info]:  | document: "performance/1k-text/"
INFO     │        │  ┕━ interpret_with_line_number [ 134ms | 68.40% ]
INFO     │        │     ┕━ i [info]:  | msg: "ftd: interpreting" | doc: "performance/1k-text/"
INFO     │        ┝━ from_interpreter [ 24.9ms | 0.34% / 12.70% ]
INFO     │        │  ┕━ execute [ 24.2ms | 0.00% / 12.37% ]
INFO     │        │     ┕━ execute_from_instructions_loop [ 24.2ms | 12.37% ]
INFO     │        ┝━ from_rt [ 3.58ms | 1.83% ]
INFO     │        ┕━ from_node_data [ 8.89ms | 4.53% ]
INFO     ┕━ i [info]: before executing proxy: file-status: 200 OK, path: 1k-text/

@AbrarNitk
Copy link
Contributor Author

AbrarNitk commented Jan 16, 2023

With 10K -- ftd.text

Logs

total: 13s
interpret_with_line_number: 12.5s, taking most of the time
from_interpreter: 360ms
from_rt: 34ms
from_node_data: 75ms

INFO i [info]: Starting 8 workers
INFO i [info]: Tokio runtime found; starting in existing Tokio runtime
replace_markers in 5.469166ms
INFO   route [ 13.0s | 0.01% / 100.00% ]
INFO ┝━ i [info]:  | method: "GET" | uri: "/10k-text/"
INFO ┕━ serve [ 13.0s | 0.00% / 99.99% ]
INFO    ┝━ Config::read [ 18.3ms | 0.14% ]
INFO    ┝━ serve_file [ 13.0s | 0.00% / 99.85% ]
INFO    │  ┝━ get_file_and_package_by_id [ 368µs | 0.00% / 0.00% ]
INFO    │  │  ┝━ i [info]:  | path: "10k-text/"
INFO    │  │  ┕━ resolve_by_id [ 275µs | 0.00% / 0.00% ]
INFO    │  │     ┝━ i [info]:  | id: "10k-text/"
INFO    │  │     ┕━ fs_fetch_by_id [ 24.5µs | 0.00% / 0.00% ]
INFO    │  │        ┕━ fs_fetch_by_file_name [ 19.5µs | 0.00% ]
INFO    │  │           ┕━ i [info]:  | document: "10k-text.ftd"
INFO    │  ┕━ read_ftd [ 13.0s | 0.00% / 99.84% ]
INFO    │     ┝━ i [info]:  | document: "10k-text.ftd"
INFO    │     ┕━ read_ftd_2022 [ 13.0s | 0.08% / 99.84% ]
INFO    │        ┝━ interpret_helper [ 12.5s | 0.00% / 96.16% ]
INFO    │        │  ┝━ i [info]:  | document: "performance/10k-text/"
INFO    │        │  ┕━ interpret_with_line_number [ 12.5s | 96.16% ]
INFO    │        │     ┕━ i [info]:  | msg: "ftd: interpreting" | doc: "performance/10k-text/"
INFO    │        ┝━ from_interpreter [ 360ms | 0.07% / 2.76% ]
INFO    │        │  ┕━ execute [ 351ms | 0.00% / 2.70% ]
INFO    │        │     ┕━ execute_from_instructions_loop [ 351ms | 2.70% ]
INFO    │        ┝━ from_rt [ 34.2ms | 0.26% ]
INFO    │        ┕━ from_node_data [ 75.3ms | 0.58% ]
INFO    ┕━ i [info]: before executing proxy: file-status: 200 OK, path: 10k-text/

@AbrarNitk
Copy link
Contributor Author

AbrarNitk commented Jan 16, 2023

With 50K -- ftd.text

Logs

total: 330s
interpret_with_line_number: 324s, taking most of the time
continue_processing: 7s
from_interpreter: 4.7s
from_rt: 184ms
from_node_data: 375ms

INFO i [info]: Starting 8 workers
INFO i [info]: Tokio runtime found; starting in existing Tokio runtime
replace_markers in 36.218208ms
INFO route [ 330s | 0.00% / 100.00% ]
INFO ┝━ i [info]:  | method: "GET" | uri: "/50k-text/"
INFO ┕━ serve [ 330s | 0.00% / 100.00% ]
INFO    ┝━ Config::read [ 10.0ms | 0.00% ]
INFO    ┝━ serve_file [ 330s | 0.00% / 100.00% ]
INFO    │  ┝━ get_file_and_package_by_id [ 104µs | 0.00% / 0.00% ]
INFO    │  │  ┝━ i [info]:  | path: "50k-text/"
INFO    │  │  ┕━ resolve_by_id [ 20.8µs | 0.00% / 0.00% ]
INFO    │  │     ┝━ i [info]:  | id: "50k-text/"
INFO    │  │     ┕━ fs_fetch_by_id [ 18.5µs | 0.00% / 0.00% ]
INFO    │  │        ┕━ fs_fetch_by_file_name [ 15.1µs | 0.00% ]
INFO    │  │           ┕━ i [info]:  | document: "50k-text.ftd"
INFO    │  ┕━ read_ftd [ 330s | 0.00% / 100.00% ]
INFO    │     ┝━ i [info]:  | document: "50k-text.ftd"
INFO    │     ┕━ read_ftd_2022 [ 330s | 0.02% / 100.00% ]
INFO    │        ┝━ interpret_helper [ 324s | 0.00% / 98.35% ]
INFO    │        │  ┝━ i [info]:  | document: "performance/50k-text/"
INFO    │        │  ┕━ interpret_with_line_number [ 324s | 0.01% / 98.35% ]
INFO    │        │     ┝━ i [info]:  | msg: "ftd: interpreting" | doc: "performance/50k-text/"
INFO    │        │     ┝━ parse_with_line_number [ 317s | 96.05% ]
INFO    │        │     ┕━ continue_processing [ 7.55s | 2.29% ]
INFO    │        ┝━ from_interpreter [ 4.83s | 0.04% / 1.46% ]
INFO    │        │  ┕━ execute [ 4.70s | 0.00% / 1.43% ]
INFO    │        │     ┕━ execute_from_instructions_loop [ 4.70s | 1.43% ]
INFO    │        ┝━ from_rt [ 184ms | 0.06% ]
INFO    │        ┕━ from_node_data [ 375ms | 0.11% ]
INFO    ┕━ i [info]: before executing proxy: file-status: 200 OK, path: 50k-text/

@AbrarNitk AbrarNitk changed the title ftd:0.3: Performance with -- ftd.text ftd:0.3: Performance Testing Jan 16, 2023
@AbrarNitk
Copy link
Contributor Author

With 100 components call

Logs

total: 94ms
interpret_with_line_number: 75ms, taking most of the time
continue_processing: 9ms
from_interpreter: 6.03ms
from_rt: < 1ms
from_node_data: 5ms
html size: 103kB
latency in browser: 99ms

INFO  i [info]: Starting 8 workers
INFO  i [info]: Tokio runtime found; starting in existing Tokio runtime
INFO  route [ 93.7ms | 0.08% / 100.00% ]
INFO  ┝━ i [info]:  | method: "GET" | uri: "/component-calling/"
INFO  ┕━ serve [ 93.6ms | 0.09% / 99.92% ]
INFO     ┝━ Config::read [ 6.10ms | 6.51% ]
INFO     ┝━ serve_file [ 87.4ms | 0.03% / 93.32% ]
INFO     │  ┝━ get_file_and_package_by_id [ 171µs | 0.15% / 0.18% ]
INFO     │  │  ┝━ i [info]:  | path: "component-calling/"
INFO     │  │  ┕━ resolve_by_id [ 29.3µs | 0.01% / 0.03% ]
INFO     │  │     ┝━ i [info]:  | id: "component-calling/"
INFO     │  │     ┕━ fs_fetch_by_id [ 23.9µs | 0.01% / 0.03% ]
INFO     │  │        ┕━ fs_fetch_by_file_name [ 15.1µs | 0.02% ]
INFO     │  │           ┕━ i [info]:  | document: "component-calling.ftd"
INFO     │  ┕━ read_ftd [ 87.2ms | 0.01% / 93.11% ]
INFO     │     ┝━ i [info]:  | document: "component-calling.ftd"
INFO     │     ┕━ read_ftd_2022 [ 87.2ms | 0.80% / 93.11% ]
INFO     │        ┝━ interpret_helper [ 74.6ms | 0.01% / 79.63% ]
INFO     │        │  ┝━ i [info]:  | document: "performance/component-calling/"
INFO     │        │  ┕━ interpret_with_line_number [ 74.6ms | 0.66% / 79.62% ]
INFO     │        │     ┝━ i [info]:  | msg: "ftd: interpreting" | doc: "performance/component-calling/"
INFO     │        │     ┝━ parse_with_line_number [ 65.1ms | 69.50% ]
INFO     │        │     ┕━ continue_processing [ 8.86ms | 9.46% ]
INFO     │        ┝━ from_interpreter [ 6.03ms | 0.00% / 6.43% ]
INFO     │        │  ┕━ execute [ 6.02ms | 0.00% / 6.43% ]
INFO     │        │     ┕━ execute_from_instructions_loop [ 6.02ms | 6.43% ]
INFO     │        ┝━ from_rt [ 820µs | 0.87% ]
INFO     │        ┕━ from_node_data [ 5.03ms | 5.37% ]
INFO     ┕━ i [info]: before executing proxy: file-status: 200 OK, path: component-calling/

@AbrarNitk
Copy link
Contributor Author

AbrarNitk commented Jan 16, 2023

With 1k components call

Stackoverflow Error Occurred

Terminal Output

❯ fpm serve
### Server Started ###
Go to: http://127.0.0.1:8000
### Configured tracing ###
INFO     i [info]: Starting 8 workers
INFO     i [info]: Tokio runtime found; starting in existing Tokio runtime

thread 'actix-server worker 0' has overflowed its stack
fatal runtime error: stack overflow
[1]    80693 abort      fpm serve

Steps to reproduce

  • Checkout to the above given PRs of FPM and FTD.
  • cd examples/performance/scripts and run python comp-call.py 1000 to generate FTD file with 1k components
  • cd examples/performance and run fpm serve and open the URL http://127.0.0.1:8000/component-calling/

@AbrarNitk
Copy link
Contributor Author

AbrarNitk commented Jan 16, 2023

With 200 recursive component call

Logs

  • 1.32s pretty fast
  • html size: 71.1MB
  • latency in browser: 2.36s
### Server Started ###
Go to: http://127.0.0.1:8000
### Configured tracing ###
INFO route [ 1.32s | 0.00% / 100.00% ]
INFO ┝━ i [info]:  | method: "GET" | uri: "/comp-rec-call/"
INFO ┕━ serve [ 1.32s | 0.00% / 100.00% ]
INFO    ┝━ Config::read [ 7.23ms | 0.55% ]
INFO    ┝━ serve_file [ 1.31s | 0.00% / 99.44% ]
INFO    │  ┝━ get_file_and_package_by_id [ 160µs | 0.01% / 0.01% ]
INFO    │  │  ┝━ i [info]:  | path: "comp-rec-call/"
INFO    │  │  ┕━ resolve_by_id [ 30.1µs | 0.00% / 0.00% ]
INFO    │  │     ┝━ i [info]:  | id: "comp-rec-call/"
INFO    │  │     ┕━ fs_fetch_by_id [ 25.1µs | 0.00% / 0.00% ]
INFO    │  │        ┕━ fs_fetch_by_file_name [ 16.9µs | 0.00% ]
INFO    │  │           ┕━ i [info]:  | document: "comp-rec-call.ftd"
INFO    │  ┕━ read_ftd [ 1.31s | 0.00% / 99.43% ]
INFO    │     ┝━ i [info]:  | document: "comp-rec-call.ftd"
INFO    │     ┕━ read_ftd_2022 [ 1.31s | 18.98% / 99.43% ]
INFO    │        ┝━ interpret_helper [ 1.28ms | 0.00% / 0.10% ]
INFO    │        │  ┝━ i [info]:  | document: "performance/comp-rec-call/"
INFO    │        │  ┕━ interpret_with_line_number [ 1.28ms | 0.05% / 0.10% ]
INFO    │        │     ┝━ i [info]:  | msg: "ftd: interpreting" | doc: "performance/comp-rec-call/"
INFO    │        │     ┝━ parse_with_line_number [ 191µs | 0.01% ]
INFO    │        │     ┕━ continue_processing [ 430µs | 0.03% ]
INFO    │        ┝━ from_interpreter [ 381ms | 0.00% / 28.92% ]
INFO    │        │  ┕━ execute [ 381ms | 0.00% / 28.92% ]
INFO    │        │     ┕━ execute_from_instructions_loop [ 381ms | 28.92% ]
INFO    │        ┝━ from_rt [ 2.48ms | 0.19% ]
INFO    │        ┕━ from_node_data [ 675ms | 51.24% ]
INFO    ┕━ i [info]: before executing proxy: file-status: 200 OK, path: comp-rec-call/

@AbrarNitk
Copy link
Contributor Author

AbrarNitk commented Jan 16, 2023

With 250 recursive component call

Stackoverflow Error Occurred

Terminal Output

### Server Started ###
Go to: http://127.0.0.1:8000
### Configured tracing ###
INFO     i [info]: Starting 8 workers
INFO     i [info]: Tokio runtime found; starting in existing Tokio runtime

thread 'actix-server worker 0' has overflowed its stack
fatal runtime error: stack overflow
[1]    85486 abort      fpm serve

Steps To Reproduce

  • Checkout to the above given PRs of FPM and FTD.
  • cd examples/performance/scripts and run python comp-call-recur.py 250 to generate FTD file
  • cd examples/performance and run fpm serve and open the URL http://127.0.0.1:8000/comp-rec-call/

@AbrarNitk
Copy link
Contributor Author

AbrarNitk commented Jan 17, 2023

Loop With Len 10K

  • Each element in the list was a string with a length of 100
  • List Data Size: 1040000B => ~1MB
  • Used a get-data processor to get the list of data from the processor body

Logs

total: 6.3s
interpret_with_line_number: 15.5ms
continue_processing: less than an ms
from_interpreter: 6s, taking most of the time
from_rt: 41ms
from_node_data: 105ms
html size: 6.4MB
browser latency: 7s

### Server Started ###
Go to: http://127.0.0.1:8000
### Configured tracing ###
INFO     i [info]: Starting 8 workers
INFO     i [info]: Tokio runtime found; starting in existing Tokio runtime
INFO     route [ 6.26s | 0.00% / 100.00% ]
INFO     ┝━ i [info]:  | method: "GET" | uri: "/performance/loop/"
INFO     ┕━ serve [ 6.26s | 0.00% / 100.00% ]
INFO        ┝━ Config::read [ 6.55ms | 0.10% ]
INFO        ┝━ serve_file [ 6.25s | 0.00% / 99.89% ]
INFO        │  ┝━ get_file_and_package_by_id [ 441µs | 0.01% / 0.01% ]
INFO        │  │  ┝━ i [info]:  | path: "performance/loop/"
INFO        │  │  ┕━ resolve_by_id [ 36.7µs | 0.00% / 0.00% ]
INFO        │  │     ┝━ i [info]:  | id: "/loop/"
INFO        │  │     ┕━ fs_fetch_by_id [ 30.8µs | 0.00% / 0.00% ]
INFO        │  │        ┕━ fs_fetch_by_file_name [ 18.5µs | 0.00% ]
INFO        │  │           ┕━ i [info]:  | document: "loop.ftd"
INFO        │  ┕━ read_ftd [ 6.25s | 0.00% / 99.88% ]
INFO        │     ┝━ i [info]:  | document: "loop.ftd"
INFO        │     ┕━ read_ftd_2022 [ 6.25s | 0.45% / 99.88% ]
INFO        │        ┝━ interpret_helper [ 27.4ms | 0.00% / 0.44% ]
INFO        │        │  ┝━ i [info]:  | document: "performance/loop/"
INFO        │        │  ┝━ interpret_with_line_number [ 15.5ms | 0.01% / 0.25% ]
INFO        │        │  │  ┝━ i [info]:  | msg: "ftd: interpreting" | doc: "performance/loop/"
INFO        │        │  │  ┝━ parse_with_line_number [ 14.2ms | 0.23% ]
INFO        │        │  │  ┕━ continue_processing [ 621µs | 0.01% ]
INFO        │        │  ┝━ fpm::stuck-on-import [ 8.33µs | 0.00% ]
INFO        │        │  ┝━ continue_after_import [ 8.64ms | 0.00% / 0.14% ]
INFO        │        │  │  ┝━ parse_with_line_number [ 205µs | 0.00% ]
INFO        │        │  │  ┕━ continue_processing [ 8.43ms | 0.13% ]
INFO        │        │  ┝━ fpm::stuck-on-processor [ 2.33ms | 0.04% ]
INFO        │        │  │  ┕━ i [info]:  | msg: "stuck-on-processor" | doc: "performance/loop/" | processor: "get-data"
INFO        │        │  ┕━ continue_after_processor [ 901µs | 0.00% / 0.01% ]
INFO        │        │     ┕━ continue_processing [ 728µs | 0.01% ]
INFO        │        ┝━ from_interpreter [ 6.05s | 0.00% / 96.65% ]
INFO        │        │  ┕━ execute [ 6.05s | 0.00% / 96.65% ]
INFO        │        │     ┕━ execute_from_instructions_loop [ 6.05s | 96.49% / 96.65% ]
INFO        │        │        ┕━ get_loop_instructions [ 10.2ms | 0.16% ]
INFO        │        ┝━ from_rt [ 41.8ms | 0.67% ]
INFO        │        ┕━ from_node_data [ 105ms | 1.68% ]
INFO        ┕━ i [info]: before executing proxy: file-status: 200 OK, path: performance/loop/

@AbrarNitk
Copy link
Contributor Author

AbrarNitk commented Jan 17, 2023

Loop With Len 10K

  • Each element in the list was a string with a length of 1000
  • List Data Size: 10040000B => ~10MB
  • Used a get-data processor to get the list of data from the processor body

Logs

total: 20s
ftd: 20s
interpret_with_line_number: 110ms
continue_processing: 3ms
from_interpreter: 19.6s, taking most of the time
from_rt: 45ms
from_node_data: 194ms
html size: 25MB
browser latency: 23s

### Server Started ###
Go to: http://127.0.0.1:8000
### Configured tracing ###
INFO     i [info]: Starting 8 workers
INFO     i [info]: Tokio runtime found; starting in existing Tokio runtime
INFO     route [ 20.2s | 0.00% / 100.00% ]
INFO     ┝━ i [info]:  | method: "GET" | uri: "/performance/loop/"
INFO     ┕━ serve [ 20.2s | 0.00% / 100.00% ]
INFO        ┝━ Config::read [ 8.17ms | 0.04% ]
INFO        ┝━ serve_file [ 20.2s | 0.00% / 99.96% ]
INFO        │  ┝━ get_file_and_package_by_id [ 492µs | 0.00% / 0.00% ]
INFO        │  │  ┝━ i [info]:  | path: "performance/loop/"
INFO        │  │  ┕━ resolve_by_id [ 45.0µs | 0.00% / 0.00% ]
INFO        │  │     ┝━ i [info]:  | id: "/loop/"
INFO        │  │     ┕━ fs_fetch_by_id [ 39.5µs | 0.00% / 0.00% ]
INFO        │  │        ┕━ fs_fetch_by_file_name [ 26.7µs | 0.00% ]
INFO        │  │           ┕━ i [info]:  | document: "loop.ftd"
INFO        │  ┕━ read_ftd [ 20.2s | 0.00% / 99.95% ]
INFO        │     ┝━ i [info]:  | document: "loop.ftd"
INFO        │     ┕━ read_ftd_2022 [ 20.2s | 0.70% / 99.95% ]
INFO        │        ┝━ interpret_helper [ 200ms | 0.00% / 0.99% ]
INFO        │        │  ┝━ i [info]:  | document: "performance/loop/"
INFO        │        │  ┝━ interpret_with_line_number [ 110ms | 0.00% / 0.55% ]
INFO        │        │  │  ┝━ i [info]:  | msg: "ftd: interpreting" | doc: "performance/loop/"
INFO        │        │  │  ┝━ parse_with_line_number [ 105ms | 0.52% ]
INFO        │        │  │  ┕━ continue_processing [ 4.79ms | 0.02% ]
INFO        │        │  ┝━ fpm::stuck-on-import [ 7.08µs | 0.00% ]
INFO        │        │  ┝━ continue_after_import [ 75.0ms | 0.00% / 0.37% ]
INFO        │        │  │  ┝━ parse_with_line_number [ 199µs | 0.00% ]
INFO        │        │  │  ┕━ continue_processing [ 74.8ms | 0.37% ]
INFO        │        │  ┝━ fpm::stuck-on-processor [ 10.7ms | 0.05% ]
INFO        │        │  │  ┕━ i [info]:  | msg: "stuck-on-processor" | doc: "performance/loop/" | processor: "get-data"
INFO        │        │  ┕━ continue_after_processor [ 3.43ms | 0.00% / 0.02% ]
INFO        │        │     ┕━ continue_processing [ 2.47ms | 0.01% ]
INFO        │        ┝━ from_interpreter [ 19.6s | 0.00% / 97.09% ]
INFO        │        │  ┕━ execute [ 19.6s | 0.00% / 97.09% ]
INFO        │        │     ┕━ execute_from_instructions_loop [ 19.6s | 97.04% / 97.09% ]
INFO        │        │        ┕━ get_loop_instructions [ 11.0ms | 0.05% ]
INFO        │        ┝━ from_rt [ 44.9ms | 0.22% ]
INFO        │        ┕━ from_node_data [ 194ms | 0.96% ]
INFO        ┕━ i [info]: before executing proxy: file-status: 200 OK, path: performance/loop/

@AbrarNitk AbrarNitk reopened this Jan 17, 2023
@AbrarNitk AbrarNitk reopened this Jan 17, 2023
@fastn-stack fastn-stack locked and limited conversation to collaborators Jan 17, 2023
@amitu amitu converted this issue into discussion #534 Jan 17, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
1 participant