one hint on leetcode & golang memory calculations:...
# wayfolk
a
one hint on leetcode & golang memory calculations: Looks like leetcode does not run GC before executing your code, which is likely CPU usage optimization on their side. Having that said, it makes your memory usage results skewed. Looking at some of the provided examples, some people add
runtime.GC()
to their functions, which moves them up. So, if you really want to get closer to fair comparison, especially for tasks that require O(1) for space, keep this in mind. The side effect of forcing GC is increased runtime, so you may want to submit with it and then without to check time utilization. For time calculations: The results aren’t super clean either as they likely include some extra time and not just start / stop on your function as re-submitting it twice may show way better time, so there is some form of caching involved
j
i thought you were taking 2 months lol meme
a
I’m taking two months from going “all-in”, I still want to allow a couple of hours a day to practice something, otherwise I’ll just go mad 😂
j
i get it. i'll warn you, that's how it started on my end - an hour here, an hour there and now my entire week is interviews 🙂
p
Practicing can take a lot of time 😄
t
I am betting Andrii has more self control .. 😉
a
It’s a struggle, Tom 😂
j
it's true, i do go all in once i get started. it's a blessing and a curse
p
Jordan good luck and best wishes with the interviews.
j
Prakash, how is work on my temple going?
p
Jordan, I am still waiting for the offer. As soon as it comes through, the master plan will be submitted for approval.
j
Ok. Would you feel comfortable sharing your master plan for review and early socialization?