Skip to content

Instantly share code, notes, and snippets.

@acstrahl

acstrahl/crunchbase.ipynb

Created June 3, 2025 20:46
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save acstrahl/66b21e90b9a4c65506f18cf690afc987 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save acstrahl/66b21e90b9a4c65506f18cf690afc987 to your computer and use it in GitHub Desktop.
Download ZIP
Analyzing Startup Fundraising Deals from Crunchbase: Dataset optimization and memory handling DEMO
Display the source blob
Display the rendered blob
Raw
crunchbase.ipynb
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@dlong10
Copy link

dlong10 commented Jul 19, 2025

Hi both, thank you for your replies!

@joshdisu, I've changed raised_amount_usd to float32 as per your advice. I didn't realise that float32 saves more memory than int64! I wonder whether int64 is still a more appropriate datatype, given the homework question of finding a more precise datatype for raised_amount_usd. Especially as raised_amount_usd is all integer values...But, I guess if all we are concerned about is memory usage, then float32 is more appropriate?

@acstrahl, I've just posted my question in the Dataquest community, titled "Changing datatypes - Crunchbase Data Engineering" and have tagged you. Thank you for looking at this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment