Wrapper TSQL Table-valued Function is slow - sql-server

Question

I built a wrapper function that currently just calls another table-valued Function but it just added a huge amount to the execution time as Client processing time. Is there a faster way to do this?
Without wrapper:
With Wrapper:
Wrapper function:
CREATE FUNCTION [console].[getCalculosRequisita]
(
#Disponivel BIGINT,
#mediaDiaria float,
#DiasStockArtigo INT,
#DiasAntes INT,
#SaidasPorMes float,
#QtdEncomendada2Meses BIGINT,
#StockAtual BIGINT,
#QtdRequisitada BIGINT,
#caixaMinima INT
)
RETURNS #tbl TABLE
(
DiasAteRotura INT,
AcaoRequisita varchar(10),
Aconselhada BIGINT
)
AS
BEGIN
--future configuration check
--future log input
INSERT INTO #tbl SELECT DiasAteRotura, AcaoRequisita,Aconselhada
FROM [cartridge].[getCalculosRequisitaTSQL]
(
#Disponivel ,
#mediaDiaria ,
#DiasStockArtigo ,
#DiasAntes ,
#SaidasPorMes ,
#QtdEncomendada2Meses ,
#StockAtual ,
#QtdRequisitada ,
#caixaMinima
)
--future log output
RETURN
END
GO

Answer 1

Do it as an inline TVF, which is much, much faster:
CREATE FUNCTION [console].[getCalculosRequisita]
(
#Disponivel BIGINT,
#mediaDiaria float,
#DiasStockArtigo INT,
#DiasAntes INT,
#SaidasPorMes float,
#QtdEncomendada2Meses BIGINT,
#StockAtual BIGINT,
#QtdRequisitada BIGINT,
#caixaMinima INT
)
RETURNS TABLE -- WITH SCHEMABINDING -- preferable, but then you can't change the underlying function
(
DiasAteRotura INT,
AcaoRequisita varchar(10),
Aconselhada BIGINT
)
AS RETURN
(SELECT DiasAteRotura, AcaoRequisita, Aconselhada
FROM [cartridge].[getCalculosRequisitaTSQL]
(
#Disponivel ,
#mediaDiaria ,
#DiasStockArtigo ,
#DiasAntes ,
#SaidasPorMes ,
#QtdEncomendada2Meses ,
#StockAtual ,
#QtdRequisitada ,
#caixaMinima
) AS t
);
GO
Obviously, if you do this then you cannot do any other inserts. In any case logging would be impossible, so I'm not sure what you were planning on doing.
You have not given the code for the underlying function. Perhaps that can be done as an iTVF also.

Answer 2

I really appreciate the replies. They were insightfull and I will upvote them all. I just post some code here for the sharing. Happy to hear your thougts if you have suggestions.
What I really wanted was to run Python from a View, I had to go complety for another direction and I think performance just went down the drain.
It seems Python runs only from Stored Procedures... so had to go for a OPENROWSET (!?) to have it as a VIEW. Not pretty, example below:
DROP PROC IF EXISTS PythonExample;
GO
CREATE PROC PythonExample
AS
BEGIN
set nocount on
SET FMTONLY OFF
DROP TABLE [dbo].[MyRows]
CREATE TABLE [dbo].[MyRows](
[RowNum] [int] NULL
) ON [PRIMARY]
INSERT INTO [MyRows]
([RowNum])
VALUES
(1),
(2)
DECLARE #tbl1 TABLE
(
COL1 INT,
COL2 INT
)
INSERT INTO #tbl1
---ATTENTION Identing is important for Python code...
EXEC sp_execute_external_script #language =N'Python',
#script=N'
import pandas as pd
df= MyInput
df["newCol"]= df["RowNum"]*2
MyOutput = df;
',
#input_data_1_name = N'MyInput',
#input_data_1 =N'SELECT [RowNum] FROM [MyRows]', --- it seems it cannot handle a temp table
#output_data_1_name =N'MyOutput'
--WITH RESULT SETS ((MyColName int, MyColName2 int));
SELECT * FROM #tbl1
END;
GO
DROP VIEW IF EXISTS ViewExample;
GO
CREATE VIEW ViewExample
AS
SELECT * FROM OPENROWSET('SQLNCLI', 'Server=localhost;Trusted_Connection=yes;', 'exec [dbo].[PythonExample]')
GO
SELECT * FROM ViewExample