This message was deleted.
# generals
Slackbot
06/09/2023, 7:43 AMThis message was deleted.
t
Tom (Xiatech)
06/09/2023, 7:49 AM@Enrico Olivelli
Tom (Xiatech)
06/09/2023, 7:49 AMplease take a read & let me know your thoughts
e
Enrico Olivelli
06/09/2023, 7:50 AMI think that it really depends on your workload.
Enrico Olivelli
06/09/2023, 7:50 AMIf your workload is about writing to an external system (IO bound) the CPU metrics don't help
Enrico Olivelli
06/09/2023, 7:51 AMLet me catch up
Enrico Olivelli
06/09/2023, 7:51 AMWith this thread
t
Tom (Xiatech)
06/09/2023, 7:51 AMsure - take your time
e
Enrico Olivelli
06/09/2023, 7:52 AMIs this a custom function?
Enrico Olivelli
06/09/2023, 7:52 AMOr a standard connector?
t
Tom (Xiatech)
06/09/2023, 7:52 AMit's a pulsar function
Tom (Xiatech)
06/09/2023, 7:52 AMusing the apache GO sdk
e
Enrico Olivelli
06/09/2023, 7:53 AMOh, I see.
Personally I have no experience of Go functions (and of Go lang)
t
Tom (Xiatech)
06/09/2023, 7:53 AMthat's fair enough, i think that the go SDK
Tom (Xiatech)
06/09/2023, 7:53 AMis just an SDK on top of pulsar functions 'the package'
e
Enrico Olivelli
06/09/2023, 7:53 AMDo you have a way to profile the execution and see what is consuming CPU resources?
Enrico Olivelli
06/09/2023, 7:54 AMMaybe there is something that saturates
Enrico Olivelli
06/09/2023, 7:55 AMI would run profiling tools and see what's going wrong
t
Tom (Xiatech)
06/09/2023, 7:56 AMok - so that's based on the premise that only 1 event is ingested at a time right
Tom (Xiatech)
06/09/2023, 7:56 AMand you're saying that there's something within the function that is causes a high cpu workload, that's fine
Tom (Xiatech)
06/09/2023, 7:58 AMwill investigate
e
Enrico Olivelli
06/09/2023, 7:58 AM👍
t
Tom (Xiatech)
06/09/2023, 8:03 AM@Nick Pocock interesting discussion