z-logo
Premium
The costs and benefits of multiple mating in a mostly monandrous wasp
Author(s) -
Boulton Rebecca A.,
Shuker David M.
Publication year - 2015
Publication title -
evolution
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.84
H-Index - 199
eISSN - 1558-5646
pISSN - 0014-3820
DOI - 10.1111/evo.12636
Subject(s) - biology , mating , fecundity , longevity , nasonia vitripennis , harassment , ecology , sexual conflict , parasitoid wasp , mutualism (biology) , mating system , zoology , evolutionary biology , parasitoid , hymenoptera , population , pteromalidae , demography , genetics , sociology , political science , law
The taxonomically widespread nature of polyandry remains a puzzle. Much of the empirical work regarding the costs and benefits of multiple mating to females has, for obvious reasons, relied on species that are already highly polyandrous. However, this makes it difficult to separate the processes that maintain the current level of polyandry from the processes that facilitate its expression and initiated its evolution. Here we consider the costs and benefits of polyandry in Nasonia vitripennis , a species of parasitoid wasp that is “mostly monandrous” in the wild, but which evolves polyandry under laboratory culture conditions. In a series of six experiments, we show that females gain a direct fecundity and longevity benefit from mating multiply with virgin males. Conversely, mating multiply with previously mated males actually results in a fecundity cost. Sexual harassment may also represent a significant cost of reproduction. Harassment was, however, only costly during oviposition, resulting in reduced fecundity, longevity, and disrupted sex allocation. Our results show that ecological changes, in our case associated with differences in the local mating structure in the laboratory can alter the costs and benefits of mating and harassment and potentially lead to shifts in mating patterns.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here