> For the complete documentation index, see [llms.txt](https://www.bfm-unity.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.bfm-unity.org/invest-method/group-1/cang-wei-guan-li-fang-fa.md).
# 仓位管理方法
一般常用的仓位管理方法有三种，即金字塔形仓位管理法、漏斗形仓位管理法、矩形仓位管理法。
**一、金字塔形仓位管理法**
金字塔形仓位管理法，即初始进场的资金量比较大，后市如果行情按相反方向运行，则不再加仓，如果方向一致，逐步加仓，加仓比例越来越小。仓位控制呈下方大，上方小的形态，所以叫金字塔形的仓位管理方法。其优点在于按照报酬率进行仓位控制，胜率越高动用的仓位就越高。不足之处就是在震荡市中，较难获得收益。
**二、漏斗型仓位管理法**
漏斗形仓位管理，即初始进场资金量比较小，仓位较轻，若行情按相反方向运行，后市逐步加仓，进而摊薄成本，加仓比例越来越大。这种方法，仓位控制呈下方小、上方大的一种形态。所以，可以称为漏斗形的仓位管理方法。此方法的优势在于初始风险比较小，在不爆仓的情况下，漏斗越高，盈利越可观。
不足之处则在于这种方法需建立在后市走势和判断一致的前提下，如果方向判断错误，或者方向的走势不能越过总成本位，将陷于无法获利出局的局面。
**三、矩形仓位管理法**
该方法是初次建仓时，进场的资金量，占总资金的固定比例，若行情按相反反向发展，以后逐步加仓，降低成本，加仓都遵循这个固定比例，可以称为矩形仓位管理方法。
矩形仓位管理法的优点在于，每次只增加一定比例的仓位，持仓成本逐步抬高，对风险进行平均分摊，从而实现平均化管理。持仓可以得到一个很好地控制，后市方向和判断一致的情况下，会获得丰厚的收益。
而缺点在于初始阶段，平均成本抬高较快，故而交易者很容易陷入被动局面，价格不能越过盈亏平衡点，处于被套局面。越是反向变动，持仓量就越大，当达到一定程度，必然全仓持有，而价格只要向反方向变动少许，就会导致爆仓。
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://www.bfm-unity.org/invest-method/group-1/cang-wei-guan-li-fang-fa.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.