Hugging Face
Models
Datasets
Spaces
Posts
Docs
Enterprise
Pricing
Log In
Sign Up
1
18
Hashem Elezabi
helezabi
Follow
https://hashemelezabi.github.io/
hashemelezabi
AI & ML interests
None yet
Recent Activity
Reacted to
abidlabs
's
post
with 👍
about 2 months ago
Open Models vs. Closed APIs for Software Engineers ----------------------------------------------------------------------- If you're an ML researcher / scientist, you probably don't need much convincing to use open models instead of closed APIs -- open models give you reproducibility and let you deeply investigate the model's behavior. But what if you are a software engineer building products on top of LLMs? I'd argue that open models are a much better option even if you are using them as APIs. For at least 3 reasons: 1) The most obvious reason is reliability of your product. Relying on a closed API means that your product has a single point-of-failure. On the other hand, there are at least 7 different API providers that offer Llama3 70B already. As well as libraries that abstract on top of these API providers so that you can make a single request that goes to different API providers depending on availability / latency. 2) Another benefit is eventual consistency going local. If your product takes off, it will be more economical and lower latency to have a dedicated inference endpoint running on your VPC than to call external APIs. If you've started with an open-source model, you can always deploy the same model locally. You don't need to modify prompts or change any surrounding logic to get consistent behavior. Minimize your technical debt from the beginning. 3) Finally, open models give you much more flexibility. Even if you keep using APIs, you might want to tradeoff latency vs. cost, or use APIs that support batches of inputs, etc. Because different API providers have different infrastructure, you can use the API provider that makes the most sense for your product -- or you can even use multiple API providers for different users (free vs. paid) or different parts of your product (priority features vs. nice-to-haves)
View all activity
Organizations
None yet
helezabi
's activity
All
Models
Datasets
Spaces
Papers
Collections
Community
Posts
Upvotes
Likes
liked
a Space
4 months ago
Running
77
🦓
Zebra Logic Bench
liked
a model
4 months ago
vidore/colpali
Updated
Sep 27
•
25.8k
•
384
liked
2 models
9 months ago
google/gemma-7b
Text Generation
•
Updated
Jun 27
•
224k
•
•
3.06k
bigcode/starcoderplus
Text Generation
•
Updated
Aug 21, 2023
•
1.51k
•
216
liked
a model
10 months ago
liuhaotian/llava-v1.6-34b
Image-Text-to-Text
•
Updated
May 9
•
16k
•
332
liked
2 models
over 1 year ago
chainyo/alpaca-lora-7b
Updated
24 days ago
•
32
•
68
mhhmm/codegen-6B-lora
Text Generation
•
Updated
Apr 26, 2023
•
700
•
2
liked
a dataset
over 1 year ago
openai/openai_humaneval
Viewer
•
Updated
Jan 4
•
164
•
158k
•
249
liked
2 models
over 1 year ago
bigcode/starcoder
Text Generation
•
Updated
Oct 8
•
13.8k
•
•
2.81k
AdamG012/chat-opt-1.3b-rlhf-actor-ema-deepspeed
Text Generation
•
Updated
Apr 25, 2023
•
14
•
8
liked
a dataset
over 1 year ago
stanfordnlp/SHP
Viewer
•
Updated
Oct 10, 2023
•
386k
•
1.55k
•
295
liked
3 models
over 1 year ago
openai-community/gpt2-large
Text Generation
•
Updated
Feb 19
•
1.25M
•
273
openai-community/gpt2
Text Generation
•
Updated
Feb 19
•
18.1M
•
•
2.37k
tloen/alpaca-lora-7b
Updated
Apr 4, 2023
•
440
liked
2 Spaces
over 1 year ago
Running
21
🤗
Code Eval
Runtime error
405
🪐
BigCode - Playground
liked
2 datasets
over 1 year ago
google-research-datasets/mbpp
Viewer
•
Updated
Jan 4
•
1.4k
•
154k
•
143
Anthropic/hh-rlhf
Viewer
•
Updated
May 26, 2023
•
169k
•
9.55k
•
1.21k