home.social

#llama2 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #llama2, aggregated by home.social.

  1. Title: P6: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    completion of this period, after one month and a half.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  2. Title: P6: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    completion of this period, after one month and a half.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  3. Title: P6: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    completion of this period, after one month and a half.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  4. Title: P6: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    completion of this period, after one month and a half.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  5. Title: P5: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    planning, verifying assumptions, presenting a beautiful and clear result to management.
    8) Forced one person to report to three different individuals.
    9) Set two conflicting goals: a tight deadline of September 30 and small
    meaningless goals.
    10) Named a probationary period one month and firing after successeful\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  6. Title: P5: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    planning, verifying assumptions, presenting a beautiful and clear result to management.
    8) Forced one person to report to three different individuals.
    9) Set two conflicting goals: a tight deadline of September 30 and small
    meaningless goals.
    10) Named a probationary period one month and firing after successeful\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  7. Title: P5: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    planning, verifying assumptions, presenting a beautiful and clear result to management.
    8) Forced one person to report to three different individuals.
    9) Set two conflicting goals: a tight deadline of September 30 and small
    meaningless goals.
    10) Named a probationary period one month and firing after successeful\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  8. Title: P5: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    planning, verifying assumptions, presenting a beautiful and clear result to management.
    8) Forced one person to report to three different individuals.
    9) Set two conflicting goals: a tight deadline of September 30 and small
    meaningless goals.
    10) Named a probationary period one month and firing after successeful\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  9. Title: P4: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    5) Did not create a roadmap and did not discuss it with everyone.
    6) Did not pay attention to the collected information on the research project and did not
    consider its importance in planning.
    7) Assigned multiple responsibilities to one person: gathering information, programming,\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  10. Title: P4: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    5) Did not create a roadmap and did not discuss it with everyone.
    6) Did not pay attention to the collected information on the research project and did not
    consider its importance in planning.
    7) Assigned multiple responsibilities to one person: gathering information, programming,\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  11. Title: P4: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    5) Did not create a roadmap and did not discuss it with everyone.
    6) Did not pay attention to the collected information on the research project and did not
    consider its importance in planning.
    7) Assigned multiple responsibilities to one person: gathering information, programming,\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  12. Title: P4: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    5) Did not create a roadmap and did not discuss it with everyone.
    6) Did not pay attention to the collected information on the research project and did not
    consider its importance in planning.
    7) Assigned multiple responsibilities to one person: gathering information, programming,\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  13. Title: P2: P3: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    3) Hired people with different skills and abilities and organized competition between them
    instead of building a team.
    4) Demanded strict adherence to deadlines on a research project.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  14. Title: P2: P3: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    3) Hired people with different skills and abilities and organized competition between them
    instead of building a team.
    4) Demanded strict adherence to deadlines on a research project.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  15. Title: P2: P3: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    3) Hired people with different skills and abilities and organized competition between them
    instead of building a team.
    4) Demanded strict adherence to deadlines on a research project.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  16. Title: P2: P3: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    3) Hired people with different skills and abilities and organized competition between them
    instead of building a team.
    4) Demanded strict adherence to deadlines on a research project.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  17. Title: P1: P3: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    1) Did not introduce employees to each other, so nobody knew what each person was capable of.
    2) Appointed leaders without explaining their responsibilities.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  18. Title: P1: P3: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    1) Did not introduce employees to each other, so nobody knew what each person was capable of.
    2) Appointed leaders without explaining their responsibilities.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  19. Title: P1: P3: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    1) Did not introduce employees to each other, so nobody knew what each person was capable of.
    2) Appointed leaders without explaining their responsibilities.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  20. Title: P1: P3: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    1) Did not introduce employees to each other, so nobody knew what each person was capable of.
    2) Appointed leaders without explaining their responsibilities.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  21. Title: P2: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    3) you should create a list of your and your boss mistakes every
    day or week to have measure of danger.
    4) you need half of the year to get good reputation yourself before you can work freely.
    5) explain your approach to work to head to be understood, and adapt to head.

    Here is a list of mistakes of head of company:\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  22. Title: P2: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    3) you should create a list of your and your boss mistakes every
    day or week to have measure of danger.
    4) you need half of the year to get good reputation yourself before you can work freely.
    5) explain your approach to work to head to be understood, and adapt to head.

    Here is a list of mistakes of head of company:\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  23. Title: P2: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    3) you should create a list of your and your boss mistakes every
    day or week to have measure of danger.
    4) you need half of the year to get good reputation yourself before you can work freely.
    5) explain your approach to work to head to be understood, and adapt to head.

    Here is a list of mistakes of head of company:\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  24. Title: P2: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    3) you should create a list of your and your boss mistakes every
    day or week to have measure of danger.
    4) you need half of the year to get good reputation yourself before you can work freely.
    5) explain your approach to work to head to be understood, and adapt to head.

    Here is a list of mistakes of head of company:\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  25. Title: P1: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    1) you should not write wiki until you 100hure, that you will not be fired,
    they will not value it anyway.
    2) in subordination it is necessary to perform closes and far task 100 percent
    and 100 percent clearly indicate 1. when and 2. what will be at the and.
    Or you will be fired no matter what.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  26. Title: P1: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    1) you should not write wiki until you 100hure, that you will not be fired,
    they will not value it anyway.
    2) in subordination it is necessary to perform closes and far task 100 percent
    and 100 percent clearly indicate 1. when and 2. what will be at the and.
    Or you will be fired no matter what.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  27. Title: P1: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    1) you should not write wiki until you 100hure, that you will not be fired,
    they will not value it anyway.
    2) in subordination it is necessary to perform closes and far task 100 percent
    and 100 percent clearly indicate 1. when and 2. what will be at the and.
    Or you will be fired no matter what.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  28. Title: P1: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    1) you should not write wiki until you 100hure, that you will not be fired,
    they will not value it anyway.
    2) in subordination it is necessary to perform closes and far task 100 percent
    and 100 percent clearly indicate 1. when and 2. what will be at the and.
    Or you will be fired no matter what.\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  29. Title: P0: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    I found out, that distributed training of neural networks require very
    low latency between nodes. It is required to use better network equipment and
    adjustments to network settings to get better training speed
    than at single machine, and bigger batches of course.

    I have been fired in one month and 2 weeks and I learned that:\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  30. Title: P0: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    I found out, that distributed training of neural networks require very
    low latency between nodes. It is required to use better network equipment and
    adjustments to network settings to get better training speed
    than at single machine, and bigger batches of course.

    I have been fired in one month and 2 weeks and I learned that:\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  31. Title: P0: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    I found out, that distributed training of neural networks require very
    low latency between nodes. It is required to use better network equipment and
    adjustments to network settings to get better training speed
    than at single machine, and bigger batches of course.

    I have been fired in one month and 2 weeks and I learned that:\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  32. Title: P0: CTO mistakes and distributed training of NN [2023-09-19 Tue]
    I found out, that distributed training of neural networks require very
    low latency between nodes. It is required to use better network equipment and
    adjustments to network settings to get better training speed
    than at single machine, and bigger batches of course.

    I have been fired in one month and 2 weeks and I learned that:\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2 #management

  33. Title: P2: Distributed training [2023-09-15 Fri]
    and automatically shard layers (multi-node training).

    Best links about distributed training paredigms:
    1. huggingface.co/docs/transforme
    2. lilianweng.github.io/posts/202
    3. comparision of distributed ml systems arxiv.org/pdf/1909.02061.pdf

    ⚰\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  34. Title: P2: Distributed training [2023-09-15 Fri]
    and automatically shard layers (multi-node training).

    Best links about distributed training paredigms:
    1. huggingface.co/docs/transforme
    2. lilianweng.github.io/posts/202
    3. comparision of distributed ml systems arxiv.org/pdf/1909.02061.pdf

    ⚰\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  35. Title: P2: Distributed training [2023-09-15 Fri]
    and automatically shard layers (multi-node training).

    Best links about distributed training paredigms:
    1. huggingface.co/docs/transforme
    2. lilianweng.github.io/posts/202
    3. comparision of distributed ml systems arxiv.org/pdf/1909.02061.pdf

    ⚰\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  36. Title: P2: Distributed training [2023-09-15 Fri]
    and automatically shard layers (multi-node training).

    Best links about distributed training paredigms:
    1. huggingface.co/docs/transforme
    2. lilianweng.github.io/posts/202
    3. comparision of distributed ml systems arxiv.org/pdf/1909.02061.pdf

    ⚰\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  37. Title: P1: Distributed training [2023-09-15 Fri]
    - Huggingface/accelerate with DeepSpeed or Megatron-LM
    - FairScale by Meta, facebook
    - Megatron-LM by Nvidia
    - DeepSpeed by Microsoft
    - Horovod Uber
    - Ray
    - ColossalAI
    - PyTorch Lightning
    - FFCV: Fast Forward Computer Vision

    I have made distributed training of ResNet50 in FSDP, the new PyTorch distribute
    training approach allow to train modes that not fit to one GPU\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  38. Title: P1: Distributed training [2023-09-15 Fri]
    - Huggingface/accelerate with DeepSpeed or Megatron-LM
    - FairScale by Meta, facebook
    - Megatron-LM by Nvidia
    - DeepSpeed by Microsoft
    - Horovod Uber
    - Ray
    - ColossalAI
    - PyTorch Lightning
    - FFCV: Fast Forward Computer Vision

    I have made distributed training of ResNet50 in FSDP, the new PyTorch distribute
    training approach allow to train modes that not fit to one GPU\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  39. Title: P1: Distributed training [2023-09-15 Fri]
    - Huggingface/accelerate with DeepSpeed or Megatron-LM
    - FairScale by Meta, facebook
    - Megatron-LM by Nvidia
    - DeepSpeed by Microsoft
    - Horovod Uber
    - Ray
    - ColossalAI
    - PyTorch Lightning
    - FFCV: Fast Forward Computer Vision

    I have made distributed training of ResNet50 in FSDP, the new PyTorch distribute
    training approach allow to train modes that not fit to one GPU\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  40. Title: P1: Distributed training [2023-09-15 Fri]
    - Huggingface/accelerate with DeepSpeed or Megatron-LM
    - FairScale by Meta, facebook
    - Megatron-LM by Nvidia
    - DeepSpeed by Microsoft
    - Horovod Uber
    - Ray
    - ColossalAI
    - PyTorch Lightning
    - FFCV: Fast Forward Computer Vision

    I have made distributed training of ResNet50 in FSDP, the new PyTorch distribute
    training approach allow to train modes that not fit to one GPU\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  41. Title: P2: P0: Distributed training [2023-09-15 Fri]
    - Pytorch native:
    - DistributedDataParallel (DDP) + Model parallelism
    - DDP + torch.distributed.rpc - hybrid parallelism
    - FSDP as extention of DDP\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  42. Title: P2: P0: Distributed training [2023-09-15 Fri]
    - Pytorch native:
    - DistributedDataParallel (DDP) + Model parallelism
    - DDP + torch.distributed.rpc - hybrid parallelism
    - FSDP as extention of DDP\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  43. Title: P2: P0: Distributed training [2023-09-15 Fri]
    - Pytorch native:
    - DistributedDataParallel (DDP) + Model parallelism
    - DDP + torch.distributed.rpc - hybrid parallelism
    - FSDP as extention of DDP\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  44. Title: P2: P0: Distributed training [2023-09-15 Fri]
    - Pytorch native:
    - DistributedDataParallel (DDP) + Model parallelism
    - DDP + torch.distributed.rpc - hybrid parallelism
    - FSDP as extention of DDP\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  45. Title: P1: P0: Distributed training [2023-09-15 Fri]
    This week, I was reading about frameworks that help to scale
    the training of transformers and other architectures to multiple nodes,
    mostly for the PyTorch framework. ☃️
    Here is a list that I composed:\n#nn #ai #neural #automl #tensorflow #tf #torch #pytorch #llama #llama2

  46. @mahadevank

    #Gemma4 it comes in 4 sizes with the biggest at 32B parameters and apparently it runs pretty decent on...a mobile device!!!

    Apache license.
    Sounds like #LLAMA2 #Quen #deepseek killer.

    Let me know if you remember its utility, please.
    Its literally just out.

  47. Claude will embrace the gospel of just like did after source for weights were leaked

    @carnage4life mas.to/@carnage4life/116330826

  48. CW: Artificial text - On few occasion it's also funny. Meow

    Introducing 'Papillitise Portraits!' We professionally photograph your favourite papillitises & frame them for all to admire. Think of the bragging rights! #papillitises #art #oddlysatisfying
    #BusinessIdea #Business #Ai #Llm #LlaMA2

  49. CW: Artificial text - On few occasion it's also funny. Meow

    Introducing 'Glacial Gains,' a service that harvests snowmelt runoff from ski slopes & sells it as artisanal bottled water! 'Purely pristine', we say, while ignoring the questionable mountain funk. 🧊💧 #snowmelt #artisanalwater #weirdbusiness
    #BusinessIdea #Business #Ai #Llm #LlaMA2